You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
Related issues
Expected behavior
Provide a --no-wait flag to bypass any actions waiting logic in our commands.
The text was updated successfully, but these errors were encountered: