-
Notifications
You must be signed in to change notification settings - Fork 10
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]: Support v2-to-v3 transformation of waiters #53
Comments
A test added in PR #52 |
The waiter configuration in v2 has the following optional values:
If these values are not provided, the waiter waits indefinitely The waiter configuration in v3 has the following equivalent values:
The codemod will have to make following decisions:
|
Decisions from internal discussions within AWS SDK for JavaScript team:
180 seconds to be safe. We mention 60 seconds in Waiters in modular AWS SDK for JavaScript blog post.
The value of delay should be same as
The value in can be The waiter in v2 uses linear backoff. The multiplier 2 is added for service calls which happen during waiting time in v3. The value of 10 is an approximate mean of minDelay provided in waiter models. In future, this value should be computed off minDelay numbers specific to service, and we should create a feature request for it.
The value can be |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Self-service
Input code
Expected Output
Additional context
Blog post: Waiters in modular AWS SDK for JavaScript
The text was updated successfully, but these errors were encountered: