Skip to content

feat: allow not waiting for actions #833

Open
@jooola

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

Expected behavior

Provide a --no-wait flag to bypass any actions waiting logic in our commands.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions