-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't add server name to service group members #26
Comments
Hi, Is there any update on this? Thanks |
Trying to follow up on this? Anything new for this? |
@Priteshkal unfortunately it looks to be that this provider is not actively developed by Citrix. Anyway, if you create PR of that change based on contributing guideline it will get merged (I have got some which was important for us). |
The following PR ( #29 )adds the ability to define servicegroup members by using the servername. Let us know if this solution fits your needs. |
Hi, Thank you for making this PR. I tried using this provider but here is what I noticed:
The functionality that I was looking for in my automation was the ability to create a server with a servername and an IP . (both together) and to add it to my service group on creation of my VM. I see in the code that there are if/else clause which makes it so that we can either add a server by IP or by servername but not make a server by using both those attributes together. Is there any way we could reopen this issue to add that ability? Thanks |
Hi,
I am trying to add a specific server name when I try to add a service group member to a service group using terraform. I see in the code for service group that currently the only things that are being parsed out from the arguments are:
IP Address, Port and Weight.
Can we have the ability to add a server name to this list so that its easier to find the servers in a service group by their names rather than IP address?
There is an argument that could be passed in the API call to add a server name:
d.Set("servername", data["servername"])
Thanks
The text was updated successfully, but these errors were encountered: