Skip to content

add assertions for wait_for_state / wait_for_status methods #264

@snowch

Description

@snowch

this is not valid:

hpecp epic_worker wait-for-state --state [ready] 

however, no errors are thrown even though --state (singular) is not a valid parameter.

We should allow the user to provide:

  • --state onestate
  • --states [onestate, anotherstate]

the user should provide either --state or --states. --states may be empty, i.e. []

similar for --status

This applies to all cli modules implementing wait_for_state / wait_for_status

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions