Skip to content

Error codes needs to be documented in Swagger #576

@uchennakevinm1

Description

@uchennakevinm1

All errors are handled as 500
For example: 
• Request /v1/pipelines/{{pipeline_id}}/start is returned code 500 after trying start the pipeline which don't have connectors or have only 1 connector
message: "failed to start pipeline: could not build nodes for pipeline {id} can't build pipeline without any source connectors"
• Request /v1/connectors is returned code 500 after trying create connector with an invalid configuration
"message": "failed to create connector: could not init connector: invalid plugin config: operation error S3: HeadBucket, serialization failed: serialization failed: input member Bucket must not be empty"

Maybe it could be a 400 code?
And these error messages are not documented in Swagger.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions