-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Timeout Due to 2 Min #126
Comments
amballapavankumar
changed the title
API Timeout Due to 2 min timeout
API Timeout Due to 2 Min
Jul 12, 2022
The timeout happening because of more number(132) of methods/operations for each API. |
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 GitHub<#126 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGXZJS6NJ6PQLVP7N5M4AETYF4FNNAVCNFSM53JTECT2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBSGQYDCNBSHA2Q>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: