Skip to content
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.

fix: Remove "increase max_retries" from the throttling error message #868

Merged
merged 1 commit into from
May 16, 2022
Merged

fix: Remove "increase max_retries" from the throttling error message #868

merged 1 commit into from
May 16, 2022

Conversation

shimonp21
Copy link
Contributor

@shimonp21 shimonp21 commented May 9, 2022

See context at cloudquery/cloudquery#1391.

Increasing max_retries will not have a positive effect in most cases, and will likely
only exacerbate any "hanging" issues.

🎉 Thank you for making CloudQuery awesome by submitting a PR 🎉

Summary


Use the following steps to ensure your PR is ready to be reviewed

  • Read the contribution guidelines 🧑‍🎓
  • Run go fmt to format your code 🖊
  • Update or add tests. Learn more about testing here 🧪
  • Update the docs by running go run ./docs/docs.go and committing the changes 📃
  • If adding a new resource, add relevant Terraform files in a separate PR 📂
  • Ensure the status checks below are successful ✅

@shimonp21 shimonp21 requested a review from a team as a code owner May 9, 2022 11:18
@shimonp21 shimonp21 requested review from spangenberg and roneli and removed request for a team May 9, 2022 11:18
@erezrokah
Copy link
Member

Rebasing will take care of the missing status checks

See context at https://github.com/cloudquery/cq-provider-aws/issues/853.

Increasing max_retries will not have a positive effect in most cases, and will likely
only exacerbate any "hanging" issues.
@shimonp21 shimonp21 merged commit 2c850c0 into cloudquery:main May 16, 2022
@shimonp21 shimonp21 deleted the throttling_error_message branch May 16, 2022 08:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants