Closed viktorliljequist closed 11 months ago
Correct. Rerunning the release works and sometimes it works on the first try.
Ok. This sounds more like an issue with the internals of Azure rather than a provider issue then. It might be worth raising a support request with Azure as to why the service returns a 502 error for the schema for a while after creation. Please do let us know how Azure responds as this might help others hitting a similar issue.
As a temporary workaround you could use an async wait (e.g. using await Task.Delay(1000)
) during an Apply (e.g. on the Value property) to delay the creation of the Api enough for Azure to have finished initializing the service.
Thanks we have found that the issue is on our side
Hi @viktorliljequist thanks for getting in contact.
To make sure I'm understanding this correctly ..
/swagger/v1/swagger.json
ApiManagement.Api
Value
property.Does that summarise the issue you're seeing?