You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Terraform Version
1.3.9
AzureRM Provider Version
3.39.0
Affected Resource(s)/Data Source(s)
azurerm_app_configuration_key
Terraform Configuration Files
I cannot reproduce with a simple repro, but here a simple version of the configuration I'm using
├── modules
│ └── a
│ └── main.tf
└── staging
└── main.tf
# module.MODULE_NAME.azurerm_app_configuration_key.app_kv_configs["SomeKey"] will be created
+ resource "azurerm_app_configuration_key""app_kv_configs" {
+ configuration_store_id = "/subscriptions/...."
+ content_type = (known after apply)
+ etag = (known after apply)
+ id = (known after apply)
+ key = "SomePrefix:SomeKey"
+ locked = false
+ type = "kv"
+ value = "1"
}
Plan: 151 to add, 1 to change, 0 to destroy.
Expected Behaviour
It should not try to recreate those resource
Actual Behaviour
The resources are marked to be created, even tha they exists in the state with the exact same value
Taking a look through here this is the same root-cause as #20531 - I've been taking a look into this regression and have opened #20539 (and #20536) to fix this (which has since been merged), which'll will ship in a patch release (v3.44.1) - apologies for any inconvenience caused, but you should be able to pin to last weeks release (v3.43.0) in the interim.
Since the fix for this has been merged I'm going to close this issue for the moment, but since this issue is included in the v3.44.1 milestone, a comment will be added here once the patch release becomes available.
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.
Is there an existing issue for this?
Community Note
Terraform Version
1.3.9
AzureRM Provider Version
3.39.0
Affected Resource(s)/Data Source(s)
azurerm_app_configuration_key
Terraform Configuration Files
module/a/main.tf
staging/main.tf
Debug Output/Panic Output
Expected Behaviour
It should not try to recreate those resource
Actual Behaviour
The resources are marked to be created, even tha they exists in the state with the exact same value
in state:
When I use
terraform state list
the resources that it try to create are listedSteps to Reproduce
terraform init
terraform apply
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: