-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
google_artifact_registry_repository churn with maven_config #14900
Comments
@andrew-stephens-insight can you share your debug log that contains the request and response to the api? |
b/287234450 |
@edwardmedia , I will add that later today. It's similar to #14846, but in this case it's producing destroy and re-create instead of just churn. |
I believe this PR has addressed the bug. |
Has this been released yet? The latest version is 5.0.0 and I'm still seeing issues.
|
Ah, this is an issue a few others have mentioned, independent from Terraform. If you are able to recreate the repository then this will be fixed, but in the meantime we are working on manually removing this field from existing Docker repositories. |
@Subserial could you provide more info as to why this issue was/is happening? Was there a time that a What change to the API/provider caused it to start forcing recreation of resources? You're saying that it's independent of TF, could you say what's the source of it? |
Sorry for the long delay. Yes, affected repositories had a |
Marking as resolved per #14900 (comment) |
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
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 tohashibot
, a community member has claimed the issue already.Terraform Version
Terraform v1.4.6
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Running a second plan or apply after initial successful apply should show no changes.
Actual Behavior
Plan shows the Maven repository will be destroyed and re-created even though no code changes.
The maven_config block shows that both variables are being set again, forcing replacement.
+ allow_snapshot_overwrites = false # forces replacement
+ version_policy = "VERSION_POLICY_UNSPECIFIED" # forces replacement
}
I checked the TFState. The maven_config block is not being saved in the state.
Steps to Reproduce
terraform apply
terraform plan
Note: I tried this with the google and google-beta providers.
Important Factoids
References
The text was updated successfully, but these errors were encountered: