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

Resource level retry logic #1959

Open
corymhall opened this issue Jan 2, 2025 · 2 comments
Open

Resource level retry logic #1959

corymhall opened this issue Jan 2, 2025 · 2 comments
Labels
kind/enhancement Improvements or new features

Comments

@corymhall
Copy link
Contributor

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Each AWS service has different API limits and require different retry logic. The CCAPI schema does not contain this information so we currently have global retry logic which applies to all resources.

For example the `` resource can have a large propagation delay when creating. The terraform-aws-provider has it configured to retry for up to 5 minutes. hashicorp/terraform-provider-aws@7a8669e/internal/service/ec2/vpc_route_table_association.go?plain=1#L80. It doesn't make sense to make 5 minutes the global retry limit though.

Affected area/feature

@corymhall corymhall added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team and removed needs-triage Needs attention from the triage team labels Jan 2, 2025
@corymhall
Copy link
Contributor Author

Another example pulumi/pulumi-cdk#277 where ApiGateway can only delete 1 api per 30 seconds.

@flostadler
Copy link
Contributor

Another example is SQS queues: #1983

You need to wait 1 minute after deleting a queue before creating one with the same name again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

2 participants