-
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
(aws-amplify): make customHeaders configurable. #17084
Comments
@skinny85 @ryparker Is it okay to take a dependency on Eg: If we use the above package, we can provide a better API for the customer that accepts an array of objects with the required details. |
@ayush987goyal sure, except substitute |
feat(amplify): Add support for custom headers in the App closes #17084 Refs: 1. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-amplify-app.html#cfn-amplify-app-customheaders 2. https://docs.aws.amazon.com/amplify/latest/userguide/custom-headers.html 3. https://www.npmjs.com/package/yaml ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
feat(amplify): Add support for custom headers in the App closes aws#17084 Refs: 1. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-amplify-app.html#cfn-amplify-app-customheaders 2. https://docs.aws.amazon.com/amplify/latest/userguide/custom-headers.html 3. https://www.npmjs.com/package/yaml ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Description
Configuring customHeaders in Amplify is possible in CloudFormation, but not yet supported in the construct library.
Use Case
Configure custom headers of application. (ex: security headers). We also can configure with
customHeaders.yml
file on root directory of git repository, but in this case, we cannot switch easily for each environments.Proposed Solution
Make configurable in App construct class.
Other information
No response
Acknowledge
The text was updated successfully, but these errors were encountered: