...
This is what it looks like when Terraform finds those tags, and makes a plan to delete them:
| Code Block |
|---|
# tfterraform plan aws_vpc.blank-vpc: Refreshing state... [id=vpc-cde7e0a8] ... aws_route_table_association.v2-private-1: Refreshing state... [id=rtbassoc-08f9e7ea923cc8454] Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: ~ update in-place Terraform will perform the following actions: # aws_subnet.example will be updated in-place ~ resource "aws_subnet" "example" { id = "subnet-0d705338215b4d08b" ~ tags = { - "cit:dc-arch-migration-description" = "No change." -> null - "cit:dc-arch-migration-target" = "no" -> null - "cit:dc-arch-version" = "v1" -> null - "cit:subnet-type" = "public" -> null # (1 unchanged element hidden) } ~ tags_all = { - "cit:dc-arch-migration-description" = "No change." -> null - "cit:dc-arch-migration-target" = "no" -> null - "cit:dc-arch-version" = "v1" -> null - "cit:subnet-type" = "public" -> null # (1 unchanged element hidden) } # (14 unchanged attributes hidden) } Plan: 0 to add, 1 to change, 0 to destroy. |
...