Open swiatlamiasta opened 7 months ago
I have experienced an identical issue with azurerm_linux_web_app
where the application keys (backed by keyvault) are returning different values.
If I re-run the plan there is a good chance this will work on the second on the third attempt
Providers required by configuration: . ├── provider[registry.terraform.io/hashicorp/azurerm] 3.105.0 ├── provider[registry.terraform.io/hashicorp/azuread] 2.50.0 ├── provider[registry.terraform.io/hashicorp/random] 3.6.2
The error output is as follows(the name of the keyvault
has been changed to protect the innocent):
Error: Provider produced inconsistent final plan
│
│ When expanding the plan for module.webapp.azurerm_linux_web_app.app to
│ include new values learned so far during apply, provider
│ "registry.terraform.io/hashicorp/azurerm" produced an invalid new value for
│ .app_settings["MY_SECRET"]: was
│ cty.StringVal("@Microsoft.KeyVault(SecretUri=[https://broken.vault.azure.net/secrets/my-secret/ed7beabbc0a1487f923b297f07656506)"),](https://broken.vault.azure.net/secrets/my-secret/ed7beabbc0a1487f923b297f07656506)%22),)
│ but now
│ cty.StringVal("@Microsoft.KeyVault(SecretUri=[https://broken.vault.azure.net/secrets/my-secret/12c5ba470af542ffa14263be5b7e0cfb)").](https://broken.vault.azure.net/secrets/my-secret/12c5ba470af542ffa14263be5b7e0cfb)%22).)
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
Also seeing this with TF v1.9.5 and AzureRM 3.112.
Is there an existing issue for this?
Community Note
Terraform Version
1.7.5
AzureRM Provider Version
3.95.0
Affected Resource(s)/Data Source(s)
azurerm_windows_web_app
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
App settings should be updated with newly generated secret.
Actual Behaviour
An error is thrown during apply
Steps to Reproduce
To reproduce this you have to run terraform apply few times.
Important Factoids
No response
References
No response