-
Notifications
You must be signed in to change notification settings - Fork 132
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
[BUG] list order not consistent in containerregistry_ip_restrictions #636
Comments
Hi @mxm-tr, this is indeed a bug and I think |
Hi, yes this could work thanks! I can create a PR next week if you want |
Yes that would be perfect |
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When applying the same container registry configuration multiple times, the ip_restrictions list is not consistent.
This causes the Managed Registries to be recreated at each apply operation.
Terraform Version
OpenTofu, but other clients should have the same issue.
OVH Terraform Provider Version
Latest version
Affected Resource(s)
Terraform Configuration Files
Any managed registry object with multiple ip_restrictions:
Expected Behavior
When applying a the same hcl configuration file multiple times, no change should be triggered.
Actual Behavior
When applying a the same hcl configuration file multiple times, changes were triggered.
Steps to Reproduce
ip_restrictions
terraform apply
multiple times without any change in the hcl definition.Additional context
A workaround is to order the items in the hcl file directly:
The text was updated successfully, but these errors were encountered: