Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cfn: Log response error status code and body #166

Merged
merged 3 commits into from
Mar 15, 2019
Merged

cfn: Log response error status code and body #166

merged 3 commits into from
Mar 15, 2019

Conversation

kontrollanten
Copy link
Contributor

@kontrollanten kontrollanten commented Feb 11, 2019

When the S3 bucket returns a non success status code: log the status code and response body to make it easier to determine what've gone wrong.

@codecov-io
Copy link

codecov-io commented Feb 11, 2019

Codecov Report

Merging #166 into master will increase coverage by 0.03%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #166      +/-   ##
==========================================
+ Coverage   77.12%   77.16%   +0.03%     
==========================================
  Files          18       18              
  Lines         634      635       +1     
==========================================
+ Hits          489      490       +1     
  Misses        104      104              
  Partials       41       41
Impacted Files Coverage Δ
cfn/response.go 70.37% <100%> (+1.13%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b3e2820...13dc7be. Read the comment docs.

@kontrollanten kontrollanten changed the title Log response error status code and body cfn: Log response error status code and body Feb 11, 2019
@bmoffatt bmoffatt merged commit 08d251d into aws:master Mar 15, 2019
@kontrollanten kontrollanten deleted the kontrollanten-err-resp branch March 16, 2019 07:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants