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
A GET after successful PUT should not return 404 (NOT FOUND). Occationally(Not 100% reproducible) the App Configuration Key resource would return 404 for GET after PUT.
…ure delete is finished, add stateWait to confirm key/feature is created (#21750)
* add app configuration checkNameAvailability
* remove retry logic in create
* go mod vendor
* increace fault tolerance
* switch list method
* add to cache when retrieve ID from endpoint
* cache app conf in create
* add state wait for key provision
* fix feature key
* fix error message and link to Azure/AppConfiguration#763
* rephrase error and log message for grammar
---------
Co-authored-by: stephybun <steph@hashicorp.com>
A GET after successful PUT should not return 404 (NOT FOUND). Occationally(Not 100% reproducible) the App Configuration Key resource would return 404 for GET after PUT.
Swagger file: https://github.com/Azure/azure-rest-api-specs/blob/280a956db30d829fa65a9c0fdede073261ad76bf/specification/appconfiguration/data-plane/Microsoft.AppConfiguration/stable/1.0/appconfiguration.json#L372-L378
detailed log from hashicorp/terraform-provider-azurerm#21939
The PUT request:
200 OK
X-Ms-Correlation-Request-Id: 79482ff0-aa1a-8be3-e0e1-8e9158d88250
X-Ms-Request-Id: ee4c4537-3097-4cc9-9c06-79b0fd945fc1
The GET request after the above PUT:
404 Not Found
X-Ms-Correlation-Request-Id: 79482ff0-aa1a-8be3-e0e1-8e9158d88250
X-Ms-Request-Id: 43e09eb2-33c7-4cf7-9fa7-edb9fbc6efc2
The text was updated successfully, but these errors were encountered: