Open amballapavankumar opened 2 years ago
The timeout happening because of more number(132) of methods/operations for each API.
Hello
Having a similar issue with a big swagger definition 1.7MB json the step fails after 2 minutes
Doing the update manually on the portal takes a while but it works.
Any ideas ?
Regards Bogdan
Don’t use azure extension. Instead use azure cli command
Thanks and Regards, Pavan Kumar Amballa
From: Bogdan Poliec @.> Sent: Thursday, November 23, 2023 4:54:46 PM To: stephaneey/azure-apim-extension @.> Cc: amballapavankumar @.>; Author @.> Subject: Re: [stephaneey/azure-apim-extension] API Timeout Due to 2 Min (Issue #126)
Hello
Having a similar issue with a big swagger definition 1.7MB json the step fails after 2 minutes [image]https://user-images.githubusercontent.com/2445870/285141788-5aedc352-f9bd-4bc1-8b40-6a0358a64349.png
Doing the update manually on the portal takes a while but it works.
Any ideas ?
Regards Bogdan
— Reply to this email directly, view it on GitHubhttps://github.com/stephaneey/azure-apim-extension/issues/126#issuecomment-1824014285, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGXZJS6NJ6PQLVP7N5M4AETYF4FNNAVCNFSM53JTECT2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBSGQYDCNBSHA2Q. You are receiving this because you authored the thread.Message ID: @.***>
We are facing an issue when the API is trying to create/update more than 2 min. Here, we are using the SKU is developer but azure says there is SLA for developer SKU. Also, other work around the provided is.
So not sure how this can be supported with the current design because we need to change the REST API call from management.azure.com to the above mentioned one also need to pass the authorization header with SAS token.