-
Notifications
You must be signed in to change notification settings - Fork 25
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
Specify security group by name #167
Conversation
} | ||
securityGroups := make([]map[string]interface{}, len(opts.SecurityGroups)) | ||
for i, groupID := range opts.SecurityGroups { | ||
securityGroups[i] = map[string]interface{}{"id": groupID} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a "vendored" bugfix for Gophercloud?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was my contrived way overriding gophercloud default behaviour expecting security group names (which turns out to be the only correct way). I just removed my override to change that into an id
field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So no, its not a bugfix. Its just crap I wrote that doesn't work that we now remove again.
@edda FYI: The spec field changes from |
Turns out specifying security groups by id doesn’t not work at all. We have to specify it by name, as the official documentation demands it.
@edda Good to merge? Will this break the UI? |
@databus23 Merge away. The UI is ready for the change. |
Turns out specifying security groups by id doesn’t not work at all.
We have to specify it by name, as the official documentation demands it.
Fixes #152 fixes #172