Difference between revisions of "Delete on termination"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
+ delete_on_termination = (known after apply) | + delete_on_termination = (known after apply) | ||
| − | + ebs_block_device { | + | + [[ebs_block_device]] { |
+ delete_on_termination = (known after apply) | + delete_on_termination = (known after apply) | ||
| − | + root_block_device { | + | + [[root_block_device]] { |
+ delete_on_termination = (known after apply) | + delete_on_termination = (known after apply) | ||
Revision as of 21:38, 17 October 2022
delete_on_termination = on
+ network_interface {
+ delete_on_termination = (known after apply)
+ ebs_block_device { + delete_on_termination = (known after apply)
+ root_block_device { + delete_on_termination = (known after apply)
See also
- Terraform, OpenTofu, Terrakube.org, Installation, Terraform AWS, Terraform GCP, Terraform commands, Terraform Cloud, Terraform Enterprise (TFE), HCL, HIL, meta-arguments, providers, modules, resource, provisioners, data sources, backends: remote backends, examples, configuration files, state files, variables, types, Terraform Registry, conditionals:
depends_on, functions, Blocks, dynamic blocks, errors, Terragrunt, Terraformer, Terratest, Terraform certifications, Terraform map type, Terraform Associate, Terraform: list type,TF_VAR_, TF_LOG, Terraform provider versioning, Terraform Style Conventions, Required version, Terraform plugin, Terraform Named Values, tags, Changelog,tfsec, tflint, Operators, Expressions:for, splat, Debugging, Namespaces, Terraform Landing Zones, CDKTF, Atmos
Advertising:
