Workspaces
Live infrastructure deployments created from Stacks, with drift detection and execution history.
Workspaces
A Workspace is a live infrastructure deployment instantiated from a Stack. It owns the actual cloud resources, Terraform state, execution history, and variable values for one deployment. Multiple workspaces can be created from the same stack (e.g. a "Production-Core" and "Staging-Core" workspace from a shared VPC stack).
Workspace Fields
| Field | Type | Description |
|---|---|---|
id | string | Unique identifier (e.g. ws-1) |
name | string | Display name (e.g. Production-Core) |
description | string | Purpose of this deployment |
status | Healthy / Drifted / Running / Failed | Current deployment state |
stack | string | Name of the Stack this was created from |
version | string | Stack version at provisioning time (e.g. v1.4.2) |
environment | Production / Staging / Development | Target environment |
provider | string | Primary cloud provider (AWS, Azure, GCP) |
accountIds | string[] | Associated cloud account IDs |
resourceIds | string[] | IDs of managed cloud resources |
resources | number | Count of managed resources |
cost | string | Estimated monthly cost (e.g. $1,240/mo) |
lastRun | string | When the last plan/apply executed |
createdBy | string | User email who created the workspace |
updatedAt | ISO datetime | Last modification timestamp |
tags | string[] | Tags for filtering and organisation |
Status Reference
| Status | Colour | Meaning |
|---|---|---|
Healthy | Green | All resources match the Terraform state |
Drifted | Amber | Live resources differ from the recorded state |
Running | Blue | A plan or apply is currently executing |
Failed | Red | The last operation failed |
Workspace Detail Tabs
Overview
Current deployment state — sync status, resource count, deployment health, drift alerts, and pending plans counter.
Files
All Terraform files (.tf, .tfvars, .tf.json) belonging to this workspace. Supports create, edit, and delete.
Pending Plans
Terraform plans awaiting review and apply. Each plan shows:
- Resources to add, change, and destroy (
+add,~change,-destroy) - Who triggered the plan and when
Execution History
Log of every plan and apply run:
- Status (
Success,Partial,Failed) - Duration
- Triggered by (user email or
"System"for scheduled runs) - Timestamp
Resources
All cloud resources managed by this workspace — type, provider, status, and age.
Variables
Input variable values provided at workspace creation time. Shows key, value, type, and whether the value is sensitive (masked).
Outputs
Terraform output values produced by the last successful apply (e.g. VPC ID, subnet CIDRs, instance IPs).
Settings
- General settings: name, description
- Drift detection schedule (cron expression + timezone)
- Auto-deprovision schedule
- Danger zone: deprovision / delete workspace
Drift Detection
MCM runs scheduled drift detection against the Terraform state. When live cloud resources differ from the recorded state, the workspace moves to Drifted status and a drift alert appears on the Overview tab. Users can trigger a manual Detect Drift run at any time.
Terraform Operations
| Operation | Description |
|---|---|
init | Download provider plugins and modules |
validate | Check .tf syntax without making API calls |
plan | Preview the changes that apply would make |
apply | Provision or update cloud resources |