DeletionPolicy / UpdateReplacePolicy resource type coverage #224
Labels
enhancement
New feature or request
Comments
luiseduardocolon
added
enhancement
PatMyron
changed the title
PatMyron
changed the title
This was referenced Nov 1, 2019
PatMyron
removed
the
database
PatMyron
added a commit
to aws-cloudformation/cloudformation-template-schema
that referenced
this issue
Sep 20, 2020
#31 https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatereplacepolicy.html Snapshot policies are only supported for a few resource types but not limiting here in hopes that Snapshot policy coverage expands: aws-cloudformation/cloudformation-coverage-roadmap#224
PatMyron
added a commit
to aws-cloudformation/cloudformation-template-schema
that referenced
this issue
Sep 21, 2020
#31 https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatereplacepolicy.html Snapshot policies are only supported for a few resource types but not limiting here in hopes that Snapshot policy coverage expands: aws-cloudformation/cloudformation-coverage-roadmap#224
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Resource types that support snapshots
Resource types that support snapshots
Missing Snapshot support for:
AWS::DynamoDB::TableAWS::DocDB::DBClusterAWS::FSx::FileSystemAWS::EMR::ClusterAWS::QLDB::LedgerMissing Delete support for:
AWS::S3::Bucket (
aws s3 rb s3://$BUCKET --force) (might timeout)AWS::ECR::Repository
I'd also like a new policy for all resource types that doesn't allow removal from the stack and stops forward progress of the stack update
All current options,
Delete/Retain/Snapshot, mean old resources can no longer be managed through CloudFormation if resource import doesn't support their resource type yet. This new policy would allow users to more easily prevent this compared with needing to evaluate change sets or write IAM stack policiesThe text was updated successfully, but these errors were encountered: