-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/azurerm: Locking around Network Security Group / Subnets #13637
Conversation
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.
LGTM, minor nit
if v, ok := d.GetOk("subnet"); ok { | ||
subnets := v.(*schema.Set).List() | ||
for _, subnet := range subnets { | ||
subnet := subnet.(map[string]interface{}) |
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.
Can we catch any errors from the interface cast here, and return?
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.
done :)
a8f06ea
to
079043d
Compare
Tests still pass - agreed to merge this with @grubernaut 👍 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Currently there's a bug regarding Network Security Groups, where trying to create a Subnet / Virtual Network / Network Security Rule (as in this example / #7986) would fail.
This PR fixes that, by only allowing a single modification to NSG's at once.
Fixes #7986