400 Bad Request errors do not show enough information to be useful #147
Description
Describe the Enhancement:
Today the sum of errors is printed out at the end of a restore. If the error is a Net::HTTPServerException there is essentially no useful information.
The literal thing I was running into was users failing to be created because of a bad email address ex.response.body #=> {"error":["email must be valid"]}. This wasn't observable with the current information being logged.
Describe the Need:
Anybody who would like to correct an issue would want to know more details about the error so the issue can be corrected.
Current Alternative
Not that I can think of other than something like pry.
Can We Help You Implement This?:
Would like some direction in terms of best way to implement. I could see creating a custom exception class for these errors and then nesting the original exception in it. Then inside the EcErrorHandler add additional ways to format the output.