Tenant projects
Every tenant project in the deploy's folder, read live from Cloud Resource Manager with your credentials — so this list is the estate as you can see it. Doctor runs the read-only checks; Destroy tears the project down for good.
Loading tenants…
Create a tenant
Fill the config, preflight it, dry-run the plan, then provision. Nothing is created until the Provision step, and provisioning starts a durable job you follow on the Jobs tab.
Template reference (template_toml)
Hand-edited — the form no longer overwrites this. “Rebuild from form” discards your edits.
Steps
Each step sends the config JSON on the left, exactly as shown.
Resume
Only for a provision that was interrupted. The server adopts the half-built project only if its own record shows that job created it; anything else is somebody else's project with the same id.
Jobs
Provisions and destroys are durable server-side rows, not this tab's memory: they survive a replica restart, any replica can answer a poll, and a job whose worker died reads interrupted rather than sitting on “running” forever. This list is only the set of ids this browser is watching — paste any job id to follow it, from any machine.
No jobs being watched. Provision or destroy a tenant, or paste a job id above.
Audit
Read-only Cloud Logging reports over IAM, billing, or one principal's footprint. Read with your credentials, from the deploy's admin control project.