Hi folks, first post on the HashiCorp forums.
Is there a way to stop Terraform – or require some sort of command line option – from destroying persistent data volumes that are part of a deployment when using the destroy command? We (Gracenote) use Terraform to manage AWS resources, and our persistent volumes are part of the Terraform code that instantiates our various services in AWS. Destroy has become a dangerous – well OK it is dangerous, but shouldn’t be in this way – command for us and particularly for some of our folks that are just users of the Terraform and not developers.
I know we could separate out the persistent volumes into a different deployments, but to me that seems hacky and problematical in its own right. The persistent data really belongs to the instances we are standing up. We’re talking about TiBs of data, by the way.
Is there some feature that already exists that I don’t know about which provides what I’m asking about? If not, would HashiCorp consider adding Terraform language to specify something like this in the deployment code?