-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Fix Keyvault network ACL with multiple subnet ids #2324
Fix Keyvault network ACL with multiple subnet ids #2324
Conversation
…vider-azurerm into fix-keyvault-multiple-subnet-ids
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 - thanks for this @leonfs :)
My pleasure @tombuildsstuff. I took it as an opportunity to try out the new Go modules. Initialising the project as a module and running the tests worked at the first attempt, great surprise. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Fixes #2129
I first added an integration test that reproduced the error by adding a new subnet to the Key Vault network ACL list. The test that creates it has two subnets, while there is another test that updates to go back to one subnet.
The function
sliceContainsValue
used to fix the problem, has also been previously used throughout the code base for similar scenarios.