Destroy a Cosmo Tech Workspace

Remember

Keep in mind that the destroy command is a macro command that removes everything deployed.

If you no longer need a Cosmo Tech workspace, you can remove it and all associated resources using the babylon destroy macro command.
This will automatically delete the following resources:

• Organizations
• Solutions
• Workspaces
• PostgreSQL schemas
• Web App

By default, it destroys the resources referenced in the current state saved in the namespace file.

To view the current context and state being used by Babylon, run the following command:

babylon namespace get-contexts

CURRENT  CONTEXT          TENANT  STATE ID  
*        test             dev     state 

When is the case you run simplement

> babylon destroy

🔥 Starting Destruction Process in namespace: dev
    → Loading configuration from Kubernetes secret...
    → Existing ID sol-9epr7jxn2ndl found. Deleting...
    ✔ Solution sol-9epr7jxn2ndl deleted
    → Found PostgreSQL service postgresql
    → Destroying postgreSQL schema for workspace w-0rnd73k2kyd5...
    → Applying kubernetes destroy job...
    → Waiting for job postgresql-destroy-w-0rnd73k2kyd5 to complete...
    → Checking job logs for errors...
    ✔ Schema destruction w_0rnd73k2kyd5 completed successfully
    → Existing ID w-0rnd73k2kyd5 found. Deleting...
    ✔ Workspace w-0rnd73k2kyd5 deleted
    → Existing ID o-841ez282ypmx found. Deleting...
    ✔ Organization o-841ez282ypmx deleted
    → Running Terraform destroy for WebApp resources...
    Acquiring state lock. This may take a few moments...
    module.chart-keycloak-client.data.kubernetes_secret.keycloak: Reading...
    module.chart-cosmotech-webapp.kubernetes_config_map.webapp: Destruction complete after 0s

    Destroy complete! Resources: 5 destroyed.
    ✔ WebApp webapp-business destroyed  

📋 Destruction Summary
  • Organization Id : DELETED
  • Solution Id     : DELETED
  • Workspace Id    : DELETED
  • Webapp Name     : DELETED

✨ Cleanup process complete

Selective Destruction

The same include/exclude philosophy applies to resource destruction. This allows you to avoid removing specific objects or to target only a single resource for deletion.

To prevent removing a specific object while destroying others, or to focus on a single one, use the following flags:

🗑️ Targeted Destruction

Destroy only a specific object (e.g., only the workspace):

babylon destroy --include workspace

🔥 Starting Destruction Process in namespace: dev
    → Loading configuration from Kubernetes secret... 
    → Existing ID w-3pkx99z1k3v found. Deleting...
    ✔ Workspace w-3pkx99z1k3v deleted

📋 Destruction Summary
    • Organization Id : o-9zmdn7w95k2
    • Solution Id     : sol-4vqjmov980v
    • Workspace Id    : DELETED

🛡️ Protected Destruction

Destroy everything except a specific object (e.g., keep the organization):

babylon destroy --exclude organization

🔥 Starting Destruction Process in namespace: dev
    → Loading configuration from Kubernetes secret...
    → Existing ID sol-4vqjmov980v found. Deleting...
    ✔ Solution sol-4vqjmov980v deleted
    ⚠ No Workspace ID found in state! skipping deletion

📋 Destruction Summary
    • Organization Id : o-9zmdn7w95k2
    • Solution Id     : DELETED
    • Workspace Id    : DELETED

✨ Cleanup process complete

Safety First

Always run babylon namespace get-contexts before a destruction command to verify which environment you are currently targeting.