Porter default error messages are too verbose for an installer experience

[raghav19]

Describe the bug

Porter error output too verbose for an installer experience
In the output image below, it can been seen that the error is in the first line alone error: no matching resources found. However, further verbose output is provided which can be avoided or removed or provided for debug purposes alone.

To Reproduce

Steps to reproduce the behavior:

1. Run any porter install that can result into an error
2. See error as given in the output

Expected behavior

It would great for the user to provide this error message over what porter provides

Porter Command and Output

Version

porter v1.2.1 (aa97c59)

[kichristensen]

Hi @raghav19,

Sorry for the late reply. I'm not sure I fully understand what you are requesting? Is it to only show the first error message? Is it related to #2284 and/or #2278?
Could you provide an example of what you would like to see instead?

[raghav19]

Hi @kichristensen, yes you are right, the mentioned issues are closely related.

As per the porter documentation, the entire experience is to create a self-contained installer for cloud native apps. So, the error message or the output should be much simpler, and more additional verbosity can print out the extended log messages. This is just my opinion.

For example, In the above screenshot, the entire chain of cascading failures is propagated as a stack and then every line is printed as a stack trace. So instead, just printing the first error message or the last one would be helpful.

Error: error running command /cnab/app /usr/bin/bash scripts/post-install.sh wait-for-controllers.sh: exit status 1

[kichristensen]

@raghav19 Thank for the explanation

[raghav19]

@kichristensen , can this be prioritized from the backlog for upcoming release of porter 1.4?

[kichristensen]

Yes I think it would be great to take a look at that