Update CLEANUP.md
This commit is contained in:
parent
443a9b9538
commit
8d4ea4ec67
|
@ -29,10 +29,28 @@ cd $FAST_PWD/02-security/
|
|||
terraform destroy
|
||||
```
|
||||
|
||||
# Networking
|
||||
# Stage 2 (Networking)
|
||||
```bash
|
||||
cd $FAST_PWD/02-networking-XXX/
|
||||
terraform destroy
|
||||
```bash
|
||||
```
|
||||
|
||||
There's a minor glitch that can surface running terraform destroy, where the service project attachments to the Shared VPC will not get destroyed even with the relevant API call succeeding. We are investigating the issue, in the meantime just manually remove the attachment in the Cloud console or via the gcloud beta compute shared-vpc associated-projects remove command when terraform destroy fails, and then relaunch the command.
|
||||
|
||||
# Stage 1 (Resource Management)
|
||||
Stage 1 is a little more complicated because of the GCS Buckets. By default terraform refuses to delete non-empty buckets, which is a good thing for your terraform state. However, it makes destruction a bit harder
|
||||
|
||||
|
||||
```bash
|
||||
cd $FAST_PWD/01-resman/
|
||||
|
||||
# remove buckets from state since terraform refuses to delete them
|
||||
for x in $(terraform state list | grep google_storage_bucket.bucket); do
|
||||
terraform state rm "$x"
|
||||
done
|
||||
|
||||
terraform destroy
|
||||
|
||||
```
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue