Booking Provisioning
When an environment has one or more Terraform projects configured for booking-time provisioning, each booking on it gets its own Provisioning section for attaching and tracking the infrastructure that backs it.
Attaching Workspaces
- An environment can have multiple booking projects, each needing its own workspace attached to the booking
- The booking shows an "N of M workspaces attached" indicator — approval is blocked until every required project has a workspace attached
- Each attached workspace has an execution order (for projects that must provision in sequence) and is either auto-apply or manual-apply
- Instead of picking an existing workspace, you can deploy a new one from a Template directly from the booking
- Workspaces can be configured to provision a buffer of time before the booking's start time, so infrastructure is ready when the booking begins
Provisioning Statuses
Each attached workspace tracks its own Terraform run status — a richer set than the booking's own status, including Queued, Pending Approval, Planning, Planned, Applying, Applied, Completed, Failed, Policy Failed, Errored, Cancelled, Destroying, and Destroyed.
After the Booking Ends
When a booking completes and its infrastructure is destroyed, a snapshot of the workspace's final state is preserved on the booking record — so you can still see what was provisioned even after the live workspace is gone.