Open kbargobdo opened 1 month ago
Hi @kbargobdo , thanks for submitting the issue!
I tried to reproduce the issue in my local but I can't, could you please provide minimal examples to reproduce it? From the error message The request for the resource '****' conflicted with an ongoing operation.
, I guess there might be other ongoing operations modifying the same App Configuration.
Hi @teowa,
We discovered that the conflict is due to the another process as you mentioned. This other process leverages an eventgrid trigger and function app to tag the app configuration resource once it sees it was created. However, we did not have this issue a few months ago and nothing with that other process has changed. Is it possible that something changed within Microsoft's APIs that are invoked by the creation of this resource?
We are investigating a few alternatives, including turning off the tagging process on app configuration resource type (providers/Microsoft.AppConfiguration/configurationStores/) or leveraging AZAPI to create the replica after a time_sleep. With these options we likely have a path forward, but any information confirming that those APIs did or did not change would be beneficial.
Hi @kbargobdo , you can submit an issue at https://github.com/Azure/AppConfiguration/issues, and the official team will help you with the API details.
Is there an existing issue for this?
Community Note
Terraform Version
1.3.7
AzureRM Provider Version
3.87
Affected Resource(s)/Data Source(s)
azurerm_app_configuration
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
App Configuration resource builds as expected, including the replica in the other region if toggled by variable
Actual Behaviour
App Configuration resource builds and then errors out when attempting to create replica.
Note that this was working a few months ago and we have not changed anything within our Azure subscriptions, modules, or versions of terraform / terragrunt / azurerm
Steps to Reproduce
terraform apply
Important Factoids
No response
References
No response