When executing commands, you might run into exceptions for whatever reason. The CLI prints the exceptions from the underlying API's to the commandline, but sometimes only a superficial message, while the actual response details from the API calls might contain a more detailed error description.
A user ran into this in issue #3524, where the actual error was revealed when adding the --debug option.
The exception details looked as follows:
"error": "{\"odata.error\":{\"code\":\"-1, System.InvalidOperationException\",\"message\":{\"lang\":\"en-US\",\"value\":\"An instance of this App already exists at the specified location.\"}}}"
What the CLI printed was:
'Error: Request failed with status code 400'
There are more types of these exception details, and it might be clearer to the user if we print the 'inner exception' as well. In this case the user would known faster what was at hand had the CLI returned the following:
Error: Request failed with status code 400' (An instance of this App already exists at the specified location.)
Or something like that. Time to discuss 👍
When executing commands, you might run into exceptions for whatever reason. The CLI prints the exceptions from the underlying API's to the commandline, but sometimes only a superficial message, while the actual response details from the API calls might contain a more detailed error description.
A user ran into this in issue #3524, where the actual error was revealed when adding the
--debugoption.The exception details looked as follows:
What the CLI printed was:
There are more types of these exception details, and it might be clearer to the user if we print the 'inner exception' as well. In this case the user would known faster what was at hand had the CLI returned the following:
Or something like that. Time to discuss 👍