search

aws-amplify / amplify-backend

Home to all tools related to Amplify's code-first DX (Gen 2) for building fullstack apps on AWS
Apache License 2.0
185 stars 62 forks source link

For hotswap, hotswappable changes in nested stacks causes the full CFN deployment #169

Closed Amplifiyer closed 1 year ago

Amplifiyer commented 1 year ago

For example, if I change a resolver in a nested stack, the API stack would need to update which triggers a fallback deployment. In other environments, it would tell me that resolver isn’t hotswappable, hence it needs to fallback to full CFN deployment.

Could not perform a hotswap deployment, because the CloudFormation template could not be resolved: We don’t support attributes of the ‘AWS::CloudFormation::Stack’ resource. This is a CDK limitation. Please report it at https://github.com/aws/aws-cdk/issues/new/choose Falling back to doing a full deployment

Amplifiyer commented 1 year ago

https://github.com/aws/aws-cdk/issues/23533

Amplifiyer commented 1 year ago

https://github.com/aws/aws-cdk/pull/27195