Permadiff on google_artifact_registry_repository.virtual_repository_config

[nphilbrook]

Community Note

• 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 the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

$ terraform version
Terraform v1.6.2
on linux_amd64
+ provider registry.terraform.io/hashicorp/google v5.3.0

Affected Resource(s)

• google_artifact_registry_repository

Terraform Configuration Files

https://gist.github.com/nphilbrook/b3b189f371bf360b7f25f8282728b16d

Debug Output

https://gist.github.com/nphilbrook/bb73df4983feca24d13b54eb70952acc

Expected Behavior

No changes.

Actual Behavior

Classic permadiff with the order of the two upstream policies being reversed.

Steps to Reproduce

1. terraform apply the config and apply it
2. terraform plan with no changes to source

Important Factoids

This was run on Terraform Enterprise. I omitted some Sentinel output from after the plan that is not relevant to this issue. I also redacted project names, SA names, etc. Nothing relevant to the bug.

b/308122977

[nphilbrook]

Thank you @Subserial and @trodge !!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.