When a heroku_build fails, query & output the build error #338
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a
heroku_build
fails, the existing error message contains a short-lived URL to download the build log. This is a frustrating experience, to have to go fetch the build log separately each time.The changeset automatically fetches the URL and sets the complete build log into the error message, so that it appears inline with all other Terraform output.
Example new
heroku_build
error output, from the the acceptance test case:Also includes a Terraform plugin SDK upgrade, because it was throwing
error: unsupported state format version: expected ["0.1" "0.2"], got "1.0"
.