client-offboarding

Workflow archives Cloud SQL and GCS data before deleting per-client resources like MIGs and static IPs, producing a final offboarding report. This prevents data leaks and unexpected costs while preserving billing records.

Yes, you can preview GCP resource deletions using a DRY-RUN mode. This safety feature generates a report of what will be removed across MIGs, Cloud SQL, and GCS buckets, requiring explicit confirmation before any actual deletion occurs.

Client offboarding removes per-client GCP resources including Managed Instance Groups (MIGs), Cloud SQL instances, GCS buckets, static IPs, firewall rules, and secrets. It systematically deletes these components to fully decommission the environment.

Yes, client offboarding relies on gcloud, psql, and Docker dependencies to execute the decommissioning workflow. These tools facilitate GCP resource management, database data archival, and script execution.

If a client offboarding script run fails midway, the workflow remains idempotent for safe re-runs. You can execute the script again without causing duplicate resource deletions or corrupting the generated archives and offboarding reports.