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

feat(cloudfront): responseHttpStatus defaults to httpStatus in errorResponses #11879

Merged
merged 3 commits into from
Dec 7, 2020

Conversation

jogold
Copy link
Contributor

@jogold jogold commented Dec 4, 2020

Make responseHttpStatus default to httpStatus if responsePagePath
is defined.

This avoids repeating the error code and is more in line with the actual
@default documentation (which actually led me to think that it
already defaulted to httpStatus).


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Make `responseHttpStatus` default to `httpStatus` if `responsePagePath`
is defined.

This avoids repeating the error code and is more in line with the actual
`@default` documentation.
@github-actions github-actions bot added the @aws-cdk/aws-cloudfront Related to Amazon CloudFront label Dec 4, 2020
@gitpod-io
Copy link

gitpod-io bot commented Dec 4, 2020

@jogold jogold changed the title feat(cloudfront): responseHttpStatus defaults to httpStatus feat(cloudfront): responseHttpStatus defaults to httpStatus in errorResponses Dec 5, 2020
@jogold
Copy link
Contributor Author

jogold commented Dec 5, 2020

Not sure this requires a README update.

Copy link
Contributor

@njlynch njlynch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Based on the docstring, it's possible this is how I originally intended it, then got distracted somewhere. :) Just one minor update.

And I agree, no need for a README update for this.


return this.errorResponses.map(errorConfig => {
if (!errorConfig.responseHttpStatus && !errorConfig.ttl && !errorConfig.responsePagePath) {
throw new Error('A custom error response without either a \'responseHttpStatus\' or \'ttl\' is not valid.');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you update this error message to be more inline with the new check?

@njlynch njlynch added the pr-linter/exempt-readme The PR linter will not require README changes label Dec 7, 2020
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
  • Commit ID: c3a42a2
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Copy link
Contributor

@njlynch njlynch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, thanks!

@mergify
Copy link
Contributor

mergify bot commented Dec 7, 2020

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot merged commit c6052ae into aws:master Dec 7, 2020
@jogold jogold deleted the cf-response-http-status-default branch December 7, 2020 13:54
skiyani pushed a commit to skiyani/aws-cdk that referenced this pull request Dec 7, 2020
…esponses (aws#11879)

Make `responseHttpStatus` default to `httpStatus` if `responsePagePath`
is defined.

This avoids repeating the error code and is more in line with the actual
`@default` documentation (which actually led me to think that it
already defaulted to `httpStatus`).


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
flochaz pushed a commit to flochaz/aws-cdk that referenced this pull request Jan 5, 2021
…esponses (aws#11879)

Make `responseHttpStatus` default to `httpStatus` if `responsePagePath`
is defined.

This avoids repeating the error code and is more in line with the actual
`@default` documentation (which actually led me to think that it
already defaulted to `httpStatus`).


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-cloudfront Related to Amazon CloudFront pr-linter/exempt-readme The PR linter will not require README changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants