Skip to content

Handle ConnectionError more gracefully #76

Description

@pederhan

As of now, whenever the CLI fails to connect to Harbor, we get a long Rich traceback, which is usually good for debugging, but in this case we definitely don't need it. We want to tell the user in no uncertain terms that we failed to connect to Harbor and that they should check the API URL.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions