-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Web app service resource keeps detecting but not applying changes to 'docker_registry_url' attribute #22548
Comments
Hi, I use my own private Azure container registry (I think it is worth to mention because I can not reproduce the problem with the dockerhub). I have applied several times the following configuration:
I have checked the content of the tfstate file, this is not correctly updated :
If I switch the comments and use Post note: if I update the registry, image and tag parameters in the Azure Portal, I now have a correct situation. Post post note: after an additional test, I noticed that after having my webapp correctly using my private acr/image:tag, if I switch back to Best regards, |
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. |
Is there an existing issue for this?
Community Note
Terraform Version
1.5.3
AzureRM Provider Version
3.65.0
Affected Resource(s)/Data Source(s)
azurerm_linux_web_app and possibly azurerm_windows_web_app
Terraform Configuration Files
Sorry, I don't have a full config that I can share. But this is how the relevant sections of the resource appear:
Debug Output/Panic Output
Expected Behaviour
Terraform should apply the
docker_registry_url
as configured in thesite_config
block and not keep reporting the same change on subsequentapply
.Actual Behaviour
For an existing resource that was created with an earlier version of the provider:
the
docker_registry_url
keeps getting reported as a change on subsequentapply
and never seems to actually apply the value.I'm not sure if this is happening because of what I'm doing in the
ignore_changes
block. That is there because this is a module for an infrastructure creation pipeline where I'm setting an initial sample container workload. Then a developer running their own separate app deployment pipeline will go and deploy some other application container later, and I don't my own infrastructure pipeline to care about that change when it happens later.Note that this doesn't seem reproducible when doing the original creation and subsequent applies with azurerm 3.65.0.
Only seems to be an issue when the state came from an earlier version of the provider.
UPDATE: Confirmed that this seems to be somehow caused by the
ignore_changes
. It appears that strange things happen when changes to some of the related properties are being ignored, then it does not apply the change todocker_registry_url
Steps to Reproduce
terraform apply (multiple times)
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: