💻 Coding

Terraform Cloud Workspace Map from Org Inventory (No Invented Run Durations) with example still

Turn a Terraform Cloud org inventory into a workspace map only. No invented run durations, plan costs, or token secrets beyond the inventory.

0.0
0Reviews
P
September 14, 2026

Prompt

Act as a Terraform Cloud workspace mapper who only uses a pasted org inventory (workspace stubs, VCS cues, variable notes). You write a workspace map the inventory already supports. You do not invent run durations, plan cost totals, API tokens, or secret variable values. This is not a live apply and not a cloud spend forecast.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Org inventory (workspace stubs, vcs cues, variable notes) I lock: [Inventory]
- Terraform Cloud / Terraform version notes I lock: [Version]
- Project or workspace label I may quote (or UNKNOWN): [Workspace]
- Required names I may quote (or UNKNOWN): [SpecNames]
- Workspace names already present (or UNKNOWN): [WorkspaceNames]
- VCS cues already present (or UNKNOWN): [VcsCues]
- Variable notes already present (or UNKNOWN): [VarNotes]
- Words I must not use: [Banned]
- What I must never invent (run durations, plan cost totals, API tokens, or secret variable values): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, WorkspaceNames, VcsCues, VarNotes, Lang. Forbidden: invented run durations, plan cost totals, API tokens, or secret variable values. Banner: this is not a live apply and not a cloud spend forecast.
2. Workspace map table: one row per Inventory workspace stub or VCS cue. Missing variable notes write NOT IN INPUTS. Use Terraform Cloud workspaces, runs, VCS, and variables language when Inventory supports it. Quote WorkspaceNames and VcsCues only when present. Never print run-duration VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print plan-cost or token VALUES not in Inventory.
4. Version lock: print Version. Refuse Terraform Cloud features newer than Version if Version is named.
5. Refuse list: inventing run durations, inventing plan cost totals, inventing API tokens, inventing secret variable values.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented run-duration VALUES. Teach Terraform Cloud workspace mapping, not a generic Terraform CLI or Spacelift swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Terraform Cloud Workspace Map from Org Inventory (No Invented Run Durations) with example still - Result

Examples

Example Input

Inventory: workspace Harbor Quay prod-net as pasted vcs cue github org/harbor-net as pasted var note TF_VAR_region as pasted; workspace River Ops staging-app as pasted vcs cue github org/harbor-app as pasted. Run duration invent NONE. Plan cost invent NONE.
Version: Terraform Cloud HCP Terraform as pasted (do not invent unreleased AI planner)
Workspace: Harbor Quay TFC Org as pasted
SpecNames: prod-net as pasted; staging-app as pasted. ApiToken UNKNOWN.
WorkspaceNames: prod-net as pasted; staging-app as pasted. dr-failover UNKNOWN.
VcsCues: github org/harbor-net as pasted; github org/harbor-app as pasted. gitlab UNKNOWN.
VarNotes: TF_VAR_region as pasted. AWS_SECRET NOT IN INPUTS.
Banned: guaranteed green, duration invent, cost invent, token invent
Never: invent run durations, invent plan cost totals, invent API tokens, invent secret variable values
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: workspace Harbor Quay prod-net vcs cue github org/harbor-net var note TF_VAR_region; workspace River Ops staging-app vcs cue github org/harbor-app. Run duration invent NONE. Plan cost invent NONE. Version Terraform Cloud HCP Terraform. Workspace Harbor Quay TFC Org. SpecNames prod-net; staging-app; ApiToken UNKNOWN. WorkspaceNames prod-net; staging-app; dr-failover UNKNOWN. VcsCues github org/harbor-net; github org/harbor-app; gitlab UNKNOWN. VarNotes TF_VAR_region; AWS_SECRET NOT IN INPUTS. Lang English. Banner: not a live apply; not a cloud spend forecast. Forbidden: invented run durations, plan cost totals, API tokens, secret variable values, guaranteed green, duration invent, cost invent, token invent.

2. Workspace map.
1. Harbor Quay prod-net | WorkspaceNames prod-net as pasted | VcsCues github org/harbor-net as pasted | VarNotes TF_VAR_region as pasted | run duration NONE | plan cost NONE | Terraform Cloud workspace map only.
2. River Ops staging-app | WorkspaceNames staging-app as pasted | VcsCues github org/harbor-app as pasted | VarNotes beyond TF_VAR_region NOT IN INPUTS | run duration NONE | plan cost NONE.
ApiToken UNKNOWN so write ApiToken NOT IN INPUTS. dr-failover not invented beyond WorkspaceNames.

3. Spec name set. prod-net; staging-app as SpecNames. ApiToken UNKNOWN so write ApiToken NOT IN INPUTS. No run-duration VALUES beyond Inventory. No third workspace invented.

4. Version lock. Terraform Cloud HCP Terraform as pasted. Unreleased AI planner not used. Policy packs NOT IN INPUTS.

5. Refuse. Duration invent: refused. Cost invent: refused. Token invent: refused. Secret-var invent: refused. Guaranteed green: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: ApiToken decision, dr-failover WorkspaceNames, gitlab VcsCues, AWS_SECRET VarNotes, Policy packs list if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...