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

Allows runtime configuration of vault provider retry delay and tries. #41

Merged
merged 15 commits into from
Jan 11, 2024

Conversation

samson-ichiban
Copy link
Contributor

@samson-ichiban samson-ichiban commented Jan 4, 2024

Due to recent issues on sync jobs caused by the Vault connectivity issues that are leading to timeouts, the ability to extend the timeout is desired. The existing implementation does not allow this at runtime due its use of decorators. This PR uses the retry_api.retry_call to facilitate runtime specification of delay and tries for retry.

gestalt/vault.py Outdated Show resolved Hide resolved
gestalt/vault.py Outdated Show resolved Hide resolved
gestalt/vault.py Outdated Show resolved Hide resolved
@samson-ichiban
Copy link
Contributor Author

Would there be any objections if I were to up the default timeout to 300 from 2? @adisunw @rtjoseph11

@adisunw
Copy link
Contributor

adisunw commented Jan 5, 2024

Would there be any objections if I were to up the default timeout to 300 from 2? @adisunw @rtjoseph11

I think I would prefer a change in the default tries rather than delay, but i'll defer to @rtjoseph11 on preferred usage.

@rtjoseph11
Copy link
Contributor

I think we should set default timeout to 60 seconds and tries to 5

…t calls. Timeout set to 60 seconds, retries to 5.
gestalt/vault.py Outdated Show resolved Hide resolved
@samson-ichiban samson-ichiban merged commit ecafd8e into master Jan 11, 2024
4 checks passed
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

Successfully merging this pull request may close these issues.

4 participants