You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
After creating the resources when the value of google_compute_region_security_policy_rule.preview changes from true to false a couple of things happen:
The google_compute_region_security_policy was duplicated on the tfstate file leaving 2 google_compute_region_security_policies one with a true value and the other with a false value for the google_compute_region_security_policy.preview argument (this happens just for google_compute_region_security_policy not for google_compute_region_security_policy_rule)
On the other hand, the google_compute_region_security_policy_rule resource was not updated and kept the value of true for the preview argument
Each time a terraform apply is executed results in a permadiff due to the last action
Community Note
Terraform Version & Provider Version(s)
Terraform v1.6.1
Affected Resource(s)
google_compute_region_security_policy_rule
Terraform Configuration
Code
Plan
Debug Output
No response
Expected Behavior
The Cloud Armor rule should have it's preview status updated to false
Actual Behavior
Steps to reproduce
terraform apply
Important Factoids
No response
References
Basically a mirror of this issue, but for the regional resource.
b/391435972
The text was updated successfully, but these errors were encountered: