Waiters should return result of last command
See original GitHub issueIs your feature request related to a problem? Please describe.
I am using the waitUntilSpotInstanceRequestFulfilled
function but it’s pointless if it does not return me the last call result so I can obtain the instance ID of the spot instance.
In general, why don’t the waiters return the payload of the last operation? I feel this would be very handy.
Describe the solution you’d like
The waiter should return the final result of the command it uses to check the status of what we are awaiting.
Describe alternatives you’ve considered
- Writing my own waiter
- Calling the same thing the waiter called again to retrieve the result…
Additional context
Add any other context or screenshots about the feature request here.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Waiters in modular AWS SDK for JavaScript
When your code does not call eventually consistent operations, you do not need waiters. In v3, the waiters are modular. You will import...
Read more >SSM waiter does not wait for the command to be ... - GitHub
this issue is regarding the SSM API which returns a command id but when the waiter requests it for its status the API...
Read more >Bash wait Command with Examples - phoenixNAP
The bash wait command is a Shell command that waits for background running processes to complete and returns the exit status.
Read more >Creating a Waiter | Cloud Deployment Manager Documentation
A Waiter resource waits for a certain success or failure condition before returning a response. For both success and failure, you set a...
Read more >Invoke-Command script block returns variable from remote ...
First of all, you should not do a Invoke-command for your local system. ... through all servers and attempt to get a value...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m not sure about the alternative “Calling the same thing the waiter called again to retrieve the result.” The APIs are eventual consistent. There is no guarantee that your read returns the same data as the one performed inside the waiter?
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.