Skip to content

Plugin Errors Collapsed into HTTP 401 #1419

@fitzthum

Description

@fitzthum

Our plugin interface uses anyhow. Any error that is returend by handle is treated as a plugin internal error, which is surfaced as a 401. In many cases, 401 doesn't match the error that was actually encountered. For example, we get a 401 if a resource is not found.

Maybe we should update the plugin interface to use thiserror so that we can better distinguish between difference cases.

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