You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if a CLI command is executed correctly, but its response is a 404, the error is returned, and automatically the help is printed.
Example:
Here, I'm trying to describe a non-existent pipeline, and notice how help is automatically printed out.
$ conduit pipelines describe foo
Error: failed to get pipeline: rpc error: code = NotFound desc = failed to get pipeline by ID: pipeline instance not found (ID: foo): pipeline instance not found
Usage:
conduit pipelines describe [flags]
Aliases:
describe, desc
Examples:
conduit pipelines describe pipeline-with-dlq
conduit pipelines desc multiple-source-with-processor
Flags:
-h, --help helpfor describe
Global Flags:
--api.grpc.address string address where Conduit is running
--config.path string path to the configuration file
failed to get pipeline: rpc error: code = NotFound desc = failed to get pipeline by ID: pipeline instance not found (ID: foo): pipeline instance not found
exit status 1
Expected output
$ conduit pipelines describe foo
pipeline instance not found (ID: foo): pipeline instance not found
What to do
We'll need to not show help if the error is expected. Only show help when there is unexpected behavior (wrong flags, wrong args, etc.).
The text was updated successfully, but these errors were encountered:
Currently, if a CLI command is executed correctly, but its response is a 404, the error is returned, and automatically the help is printed.
Example:
Here, I'm trying to describe a non-existent pipeline, and notice how help is automatically printed out.
Expected output
What to do
We'll need to not show help if the error is expected. Only show help when there is unexpected behavior (wrong flags, wrong args, etc.).
The text was updated successfully, but these errors were encountered: