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] retries implemented, or max_retries configable if retry already implemented #199

Open
FireballDWF opened this issue Jun 19, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@FireballDWF
Copy link

Is your feature request related to a problem?

"elastic: Error 503 (Service Unavailable)" is sometimes returned when the access policy creation which allows usage has not achieved eventually consistency before invocation of resource creation like opensearch_index which actually depends on the policy.

What solution would you like?

retries on 503 errors, and other transient failures.

What alternatives have you considered?

could add sleep between the two calls

Do you have any additional context?

Implement retries similar to the AWS provider behavior - https://registry.terraform.io/providers/hashicorp/aws/latest/docs#max_retries

@FireballDWF FireballDWF added enhancement New feature or request untriaged labels Jun 19, 2024
@rblcoder
Copy link
Collaborator

In aws.Config, MaxRetries is currently set to 1

MaxRetries: aws.Int(1),

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 📦 Backlog
Development

No branches or pull requests

2 participants