Skip to content

Better handling of kubectl errors #21

@seblegall

Description

@seblegall

Right now, blackbeard only output an generic error message when somthing went wrong with the kubectl apply command.

We should output the error message returned by kubectl.

Metadata

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