Description
Describe the bug
Creating an app with the customResponseHeaders
property, and then removing the property does not remove the custom headers from the app.
Regression Issue
- Select this option if this issue appears to be a regression.
Last Known Working CDK Version
No response
Expected Behavior
Removing the customResponseHeaders
property from the App construct should delete it from the Amplify app in the dashboard.
Current Behavior
The custom headers stay in their previous configuration.
Reproduction Steps
Create an example Amplify app with the customResponseHeaders
property:
new amplify.App(this, 'App', {
customResponseHeaders: [
{
pattern: '**',
headers: {
Test: 'test',
},
},
],
});
Then remove the customResponseHeaders
property, observe that the headers are still in the Amplify dashboard.
Possible Solution
Omitting CustomHeaders
in CloudFormation does not remove the headers from the app, instead we could explicitly set it to an empty string if the customResponseHeaders
property is not provided, similar to how we currently handle the basicAuth
property.
Additional Information/Context
No response
CDK CLI Version
2.162.1 (build 10aa526)
Framework Version
2.162.1-alpha.0
Node.js Version
v22.9.0
OS
macOS 14.7 (23H124)
Language
TypeScript
Language Version
TypeScript 5.6.3
Other information
No response
Activity