-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Conversation
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.
Not sure this requires a README update. |
There was a problem hiding this 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.'); |
There was a problem hiding this comment.
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?
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks!
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). |
…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*
…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*
Make
responseHttpStatus
default tohttpStatus
ifresponsePagePath
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 italready defaulted to
httpStatus
).By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license