Difference between revisions of "Example execution terraform destroy"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
+ | [[terraform destroy]] | ||
<pre> | <pre> | ||
− | |||
aws_instance.app_server: Refreshing state... [id=i-0598bc37b772faaa3] | aws_instance.app_server: Refreshing state... [id=i-0598bc37b772faaa3] | ||
Revision as of 09:55, 2 September 2021
terraform destroy
aws_instance.app_server: Refreshing state... [id=i-0598bc37b772faaa3] Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: - destroy Terraform will perform the following actions: # aws_instance.app_server will be destroyed - resource "aws_instance" "app_server" { - ami = "ami-830c94e3" -> null - arn = "arn:aws:ec2:us-west-2:72859226533:instance/i-0598bc37b772faaa3" -> null - associate_public_ip_address = true -> null - availability_zone = "us-west-2a" -> null - cpu_core_count = 1 -> null - cpu_threads_per_core = 1 -> null .../... Plan: 0 to add, 0 to change, 1 to destroy. Do you really want to destroy all resources? Terraform will destroy all your managed infrastructure, as shown above. There is no undo. Only 'yes' will be accepted to confirm. Enter a value: yes aws_instance.app_server: Destroying... [id=i-0598bc37b772faaa3] aws_instance.app_server: Still destroying... [id=i-0598bc37b772faaa3, 10s elapsed] aws_instance.app_server: Destruction complete after 30s Destroy complete! Resources: 1 destroyed.
See also
terraform
[untaint | fmt
|apply
|show
|state
|init | plan | console | output
|validate
|destroy
|debug
|import
|providers
|get
|graph
|workspaces
|resource
|login
|-var-file
|state mv
|state pull
|state push
|state replace-provider
|state rm
|force-unlock
|env
|tfe
|--version
|remote-exec
|delete on termination
| deprecated commands |terraform --help
]
Advertising: