From 8da7fbd351a7f47b9b7f93d92aa0e3528b337ae6 Mon Sep 17 00:00:00 2001 From: ajlopezn Date: Fri, 10 Jun 2022 17:16:11 +0200 Subject: [PATCH] cleanup reference in readme --- fast/stages/CLEANUP.md | 4 ++-- fast/stages/README.md | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/fast/stages/CLEANUP.md b/fast/stages/CLEANUP.md index 88469dad1..aeeed567d 100644 --- a/fast/stages/CLEANUP.md +++ b/fast/stages/CLEANUP.md @@ -1,5 +1,5 @@ -# a FAST deployment clean up -In case you require destroying FAST deployment in your organization, follow these steps. +# FAST deployment clean up +In case you require destroying a FAST deployment in your organization, follow these steps. Destruction goes in reverse order, from stage 3 to stage 0: diff --git a/fast/stages/README.md b/fast/stages/README.md index 8b0814280..d7951ba79 100644 --- a/fast/stages/README.md +++ b/fast/stages/README.md @@ -17,6 +17,8 @@ To achieve this, we rely on specific GCP functionality like [delegated role gran Refer to each stage's documentation for a detailed description of its purpose, the architectural choices made in its design, and how it can be configured and wired together to terraform a whole GCP organization. The following is a brief overview of each stage. +To destroy a previous FAST deployment follow the instructions detailed in [cleanup](CLEANUP.md). + ## Organizational level (00-01) - [Bootstrap](00-bootstrap/README.md)