Closed aabedraba closed 2 years ago
This applies to every syntax error or configuration error in Kusk, they're very hard to read, specially from the terminal and being a novice user.
From refinement: In the scenario above the output is being piped through kubectl and the error message is being generated out of our control without making a kubectl plugin.
@crjones kubectl will complain anyway if the provided string is not Kubernetes compatible... and people will double-check the output of the command to see what error is being produced. I think we should improve the reporting of errors and not letting kubectl do that.
I will close this one out since we can't do much about it.
Error messages we are sending are messed up by kubectl.
Describe the enhancement you'd like to see For example, if I tried to apply an OpenAPI with mocking and validation enabled together, the error message is unreadable
Could we make it more readable?