mitchellh/vagrant-aws — pull request #101 by jeremyharris (2013-06-20 15:17:48+00:00)
Title: Detailed error on HTTPStatusError (issue #75)

Like others, I've had the problem with the lack of detailed error. I first tried updating fog locally but the error was still "Expected(200) <=> Actual(400 Bad Request)".

Since the excon gem (dependency of the fog gem) is the one throwing the error, I thought we'd catch that and display the actual response. If there's a nicer way of doing it let me know (i.e., just showing the `response.body`? that would be amazon's response XML). I don't know any ruby so I just kinda did as much as I could. No tests either, but would love to learn.

Anyway, this revealed to me, for example, that the AMI image id I was using was apparently invalid. I grabbed it from some other tutorial as I'm learning vagrant - so who'da thunk it would be wrong?