Skip to content
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

[FEATURE REQ] A ENV variable to extractor and publisher to sleep X milliseconds between successive API call to APIM control plane #706

Closed
martin2176 opened this issue Nov 15, 2024 · 2 comments

Comments

@martin2176
Copy link

Please describe the feature.

I am anticipating that when extracting and publishing artifacts , especially when the number of resources that need to be exported and published are quite large, there is a potential of running into 429 (too many requests/rate limited) by APIM control plane or just being returned with API call errors because of the chance of overwhelming the control plane .
RFE: Can extractor and publisher support a sleep values (in milliseconds between successive api calls)

Copy link

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

@guythetechie
Copy link
Contributor

@martin2176 - we make API calls with the Azure SDK's HttpPipeline. It already handles 429 responses and has a default set of retry options. We have a feature request to make those retry options configurable in ApiOps (#254), so I'll close this issue in favor of that one.

@guythetechie guythetechie closed this as not planned Won't fix, can't repro, duplicate, stale Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants