-
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 to allow multiple rule setup in the redis firewall resource #3731
fix to allow multiple rule setup in the redis firewall resource #3731
Conversation
Works with tf.12 as well |
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.
Hi @adubnik,
Thanks for this fix! the code LGTM, however could we ad a regression test with multiple firewall rules to ensure its not broken in the future? Once thats addthis this should be good to merge 🙂
@katbyte I thought as much :) Added the multi rule test now |
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.
Thanks for adding the test @adubnik, LGTM now!
This has been released in version 1.31.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 1.31.0"
}
# ... other configuration ... |
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! |
At the moment Redis SDK return success when 2+ rules are being setup in the terraform configuration where in reality create operation does not create more than 1 rule returning success for all operations which results in the read error happening in the resourceArmRedisFirewallRuleCreateUpdate
As a fix I've added a retry logic to the resourceArmRedisFirewallRuleCreateUpdate which will loop through the create process until all reads are successful or create operation fails.
(fixes #2830)