Binding ServiceGroup to multiple VirtualServers

[sjwl]

This currently doesn't seem possible.

Binding a single netscaler_servicegroup to multiple netscaler_lbverver.

[chiradeep]

What would you suggest? Should the lbvserver parameter be a schema.TypeSet instead of schema.TypeString?

[sjwl]

Yes that would work for us. But was hoping the change would also consume only a single http connection. As it is now when we have 130+ VIPs to bind to, an equal number of service groups are created which cause some calls to fail intermittently as the max number of Netscaler connections are reached.

[paultravers]

Being able to bind a single servicegroup resource to multiple vservers would also be very useful for us.

[paultravers]

Also being able to bind a service to multiple vservers would be useful, but servicegroups should suffice in the short term.

[chiradeep]

See if this works: https://github.com/citrix/terraform-provider-netscaler/releases/tag/v0.96-alpha.2

For reducing the number of connections, we already re-use a global http.Client in the go code, which by default re-uses connections. Perhaps try and reduce the parallelism of TF
terraform apply -parallelism=n

[paultravers]

Multiple vservers appears to be working on my test server. Thanks for the quick turnaround!

[chiradeep]

@paultravers @sjwl comments on issue #6

[sjwl]

@chiradeep Multiple vservers appear to be working on our end too. Thank you very much!