Skip to content

resource options should support multi specification with better semantics #14

@ahakanbaba

Description

@ahakanbaba

The resource options https://github.com/box/wavectl/blob/master/doc/CommandReference.md#resource-options should have better semantics if they are specified multiple times.

Right now, the later specified one overwrites an earlier specified one.

I think append action here is more suitable for them.
Whatever is specified mutiple times, the implementation should AND the speficied options.

For example if the user has specified
wavectl show alert --name "Kubernetes" --name "Node[0-9]+1"
the command should only return alerts whose name match both "Kubernetes" AND "Node[0-9]+1" regular expressions

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions