Skip to content

Insufficient error messages when running lagoon ssh with -C #426

@tnelson-doghouse

Description

@tnelson-doghouse

Is your feature request related to a problem? Please describe.
One of the following error messages is less than awesome:

cli:/app$ lagoon ssh --project 'project-name' --environment 'production'
3fbfb3e6-4b5a-45a7-94be-41fcc8ddf9ba: No running pod found for service cli
cli:/app$ lagoon ssh --project 'project-name' --environment 'production' -C 'echo hi'
Error: Process exited with status 1

In particular, that second error is not useful. I spent quite a while trying to find the error in a longer command string, and then it turned out that the error in the first command was the problem.

Describe the solution you'd like
When the second command is run, it has the same error as the first command.

Describe alternatives you've considered
None, really. There's probably an even better way of doing this, but I don't know what it is. It may involve prefixing the first error with "Lagoon" (as opposed to, eg. "Shell" for the shell output)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions