DeletionPolicy Attribute - Retain

[ozbillwang]

Hi there,

Terraform Version

all

Affected Resource(s)

Please list the resources as a list, for example:

• aws_s3_bucket, s3 is a sample, this feature should be applied to most resources.
• meta-parameters: lifecycle

Terraform lifecycle has three attributes: create_before_destroy, prevent_destroy, ignore_changes, but doesn't support attribute retain which AWS CFN supported.

http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html

Terraform Configuration Files

resource "aws_s3_bucket" {
   ...
   lifecycle {
     retain = true|false
   }
}

Expected Behavior

Need retain option works as in AWS Cloudformation. Related document is at http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html

To keep a resource when its stack is deleted, specify Retain for that resource. You can use retain for any resource. For example, you can retain a nested stack, S3 bucket, or EC2 instance so that you can continue to use or modify those resources after you delete their stacks.

Actual Behavior

No this option

[dreznick]

Do we know when this going to be available?

[fricanojohnb]

This is a pretty important thing to have in TF, especially for teams working with extensive data resources. Are there any updates here or is anyone specifically working on adding this yet? This has been stale for almost two years now.

[malachantrio]

We would very much love this option as well. At the moment we are having to fudge our ci/cd deploy machines permissions so that we remove the ability for terraform to delete certain resources

[saieva]

Supporting a retain lifecycle would be useful. This might also apply to AWS Elastic IP resources that are used to access services over the Public Internet.

[sethbacon]

Long-lived databases seem like another good area for this. RDS instances, DynamoDB tables, etc. VPCs might be another resource that is long-lived in some environments and would warrant the Retain support.

[bennettp123]

This would be useful for our deployment process. It mostly uses terraform, but it also uploads our javascript bundles to S3 with immutable filenames, which are eventually cleaned up by S3 lifecycle policies. We tried using terraform for this, but it deletes previous versions which are gone from the local filesystem, so we're currently using aws-cli instead.

[ewbankkit]

Closing this Issue in this repository.
The requirements have been captured in various internal HashiCorp repository issues dealing with new Terraform lifecycle behaviors.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.