-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
fix(amplify-alpha): removing customResponseHeaders
property does not remove the headers from the app
#31844
base: main
Are you sure you want to change the base?
Conversation
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.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Exemption Request - I have updated the existing unit test, and integration test snapshots with the new default values. I'm not really sure what I could put in a new integration test, as it'd test the same values as the existing integration tests. |
The pull request linter fails with the following errors:
PRs must pass status checks before we can provide a meaningful review. If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing ✅ A exemption request has been requested. Please wait for a maintainer's review. |
Issue # (if applicable)
Closes #31783.
Reason for this change
After setting the
customResponseHeaders
property to some value in the App construct, removing it again does not remove the headers in the Amplify console.Description of changes
I have set the
customHeaders
property to a default value of an empty string. This sets the relevant CloudFormation property whencustomResponseHeaders
is not provided, therefore overriding any previous values with an empty string. I took a look at a similar issue of removing basic auth from an app and saw we did something similar there - #15243.Description of how you validated changes
Updated the existing tests with the new default value.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license