Currently, when attempting to delete a CloudFormation Stack generated by gboost create that uses cdk-nextjs-standalone, Lambda@Edge functions prohibit the deletion of the stack. CloudFormation times out and you have to wait 10-15 minutes to delete. Recommend providing a configuration option to make Lambda@Edge resources "Retain On Delete" for easy deletion of the CloudFormation stack. This will result in orphaned Lambda@Edge functions but it won't cost user much, will more just be annoying. This will be opt-in, i.e. you'll have to set environment variable or something.
bestickley
commented
1 year ago
Currently, when attempting to delete a CloudFormation Stack generated by
gboost createthat uses cdk-nextjs-standalone, Lambda@Edge functions prohibit the deletion of the stack. CloudFormation times out and you have to wait 10-15 minutes to delete. Recommend providing a configuration option to make Lambda@Edge resources "Retain On Delete" for easy deletion of the CloudFormation stack. This will result in orphaned Lambda@Edge functions but it won't cost user much, will more just be annoying. This will be opt-in, i.e. you'll have to set environment variable or something.