-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
aws_waf_rate_based_rule doesn't update rate_limit changes #9659
Comments
we're seeing this exact behaviour too trying to update the rate limits - TF reports it has mad the modification but it has not. |
Hi @vad and @connollydaire, thank you for following this issue. I was able to confirm this behavior and the linked PR should correct things. |
The related fix has been merged and will release with |
This has been released in version 3.5.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
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. Thanks! |
This issue was originally opened by @vad as hashicorp/terraform#22368. It was migrated here as a result of the provider split. The original body of the issue is below.
Terraform Version
Terraform Configuration Files
Debug Output
Relavant part:
https://gist.github.com/vad/3588212535b6a00b186bbd0dd4dd69cd
Expected Behavior
If if change
rate_limit
value I expect terraform to update the rate based rule.Actual Behavior
Terraform detects the change and actually tells me it update the rule but it didn't:
If I apply again, this repeats.
Steps to Reproduce
terraform init
terraform apply
rate_limit
terraform apply
The text was updated successfully, but these errors were encountered: