-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LZ Delete: full terraform destroy option for some or all of 1-5 folders including 0-bootstrap gcloud infrastructure - dev/org reuse #403
Labels
Comments
For example one of my first deployments of the TEF failed on 1-org because of a statefile diff between 1.3.10 and 1.7.5 - my subsequent deployment in another org was done with 1.3.10 throughout. reverse
|
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are some use cases where the entire landing zone or one of the multi-tenant folder must be deleted.
Most of these use cases are developer workflows where we repeatedly create/delete resources - more towards full integration testing.
This procedure is also required as part of a CI/CD full integration test - where the organization is reused.
Use Cases:
UC1 - triaging/fixing failed deployments will require more than one LZ per org - like in terraform-google-modules/terraform-example-foundation#1170
The text was updated successfully, but these errors were encountered: