As a API provider using the CLI, I need detailed error messages available so I can identify issues when trying to apply configuration.
Currently, the message is often limited to "error": "something went wrong" which leaves the user in the dark on what the actual problem is. At the least, just return the API response if there is not a more specific or detailed message when --debug is on.
Poor error message cases
Compiling a list of cases with poor error messages to look at what we want to handle better may be a useful aid.
- trying to enable a dataset where org doesn't match the Gateway
- invalid Product name (contains underscore)
As a API provider using the CLI, I need detailed error messages available so I can identify issues when trying to apply configuration.
Currently, the message is often limited to
"error": "something went wrong"which leaves the user in the dark on what the actual problem is. At the least, just return the API response if there is not a more specific or detailed message when--debugis on.Poor error message cases
Compiling a list of cases with poor error messages to look at what we want to handle better may be a useful aid.
something brokesomething broke