Open
Description
TL;DR
In some use cases, waiting for actions to complete does not make sens, for example deleting a server can be done in a fire and forget manner to prevent waiting too long the resource are deleted.
We proposed users to put the process in the background to continue with their scripts, but this can lead to multiple problems:
- We do not have the information if the actions that we created, was actually created without error.
- We have inconsistent behavior when deleting resources in batches, the first 10 will have the expected behavior, but the rest of the resources will still have to wait for the first batch to complete.
Related issues
- Option to disable wait for apply_firewall #613
- fix: hcloud server shutdown should wait until the server is actually shut down #489
- run command async without foreground #284
Expected behavior
Provide a --no-wait flag to bypass any actions waiting logic in our commands.
Activity