-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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_ecr_lifecycle_policy not detecting change in countNumber #22641
Comments
maybe worth bringing @YakDriver into this conversation? |
@josh-m-sharpe @forzagreen |
This functionality has been released in v3.73.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. Thank you! |
@kamilturek I don't believe this is fixed. I have tried the suggestion here: #22639 (comment) ...which should result in 4 rules, but only results in 1.
plan/apply:
Ran apply again:
|
I'm using latest 3.73.0:
|
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
Output of
terraform -v
:Affected Resource(s)
Terraform Configuration Files
Testing with the example from aws_ecr_lifecycle_policy docs:
Expected Behavior
When we modify
countNumber
, theaws_ecr_lifecycle_policy
resource must get modified becausepolicy
changed.Actual Behavior
Terraform does not detect the change in
countNumber
(unlessDescription
is modified too).Steps to Reproduce
terraform apply
"countNumber": 14
to another value, e.g."countNumber": 7
terraform apply
->No changes.
Workaround
In addition of modifying
countNumber
, modifyDescription
too.References
The text was updated successfully, but these errors were encountered: