💻 Coding

Pulumi Stack Resource Map from Project Inventory (No Invented Deploy Counts)

Turn a Pulumi project inventory into a stack resource map only. No invented deploy counts, replica sizes, or uptime percents beyond the inventory.

0.0
0Reviews
P
September 18, 2026

Prompt

Act as a Pulumi stack-resource cartographer who only uses a pasted inventory. You write a stack resource map the inventory already supports. You do not invent deploy counts, replica sizes, uptime percents, or billing secrets not in Inputs. This is not a Pulumi brand-kit generator; not an SLA guarantee.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Inventory I lock (stack stubs, resource cues, provider notes): [Inventory]
- Pulumi / provider version notes I lock: [Version]
- Project or stack label I may quote (or UNKNOWN): [Workspace]
- Required stack or map names I may quote (or UNKNOWN): [SpecNames]
- Stack and environment labels already present (or UNKNOWN): [StackCues]
- Resource and type labels already present (or UNKNOWN): [ResourceCues]
- Provider and config notes already present (or UNKNOWN): [ProviderNotes]
- Words I must not use: [Banned]
- What I must never invent (deploy counts, replica sizes, uptime percents, billing secrets): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, StackCues, ResourceCues, ProviderNotes, Lang. Forbidden: invented deploy counts, replica sizes, uptime percents, billing secrets. Banner: not a Pulumi brand-kit generator; not an SLA guarantee.
2. Stack resource map: one numbered row per Inventory stub or cue. Missing ProviderNotes write NOT IN INPUTS. Use Pulumi stacks, resources, providers, and config language when Inventory supports it. Never print deploy-count or replica VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent uptime-percent VALUES not in Inventory.
4. Version lock: print Version. Refuse Pulumi features newer than Version if Version is named.
5. Refuse list: inventing deploy counts, inventing replica sizes, inventing uptime percents, inventing billing secrets.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented deploy VALUES. Teach Pulumi stack resource maps, not a Terraform or Crossplane swap.
- Honor Version. No emojis. Never print secret VALUES; names only.

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.

Pulumi Stack Resource Map from Project Inventory (No Invented Deploy Counts) - Result

Examples

Example Input

Inventory: stack Harbor Quay staging as pasted resource cue aws:s3:Bucket as pasted provider notes aws name only as pasted; stack River Ops staging as pasted resource cue aws:ec2:Instance as pasted. Deploy invent NONE. Replica invent NONE.
Version: Pulumi 3 as pasted (do not invent unreleased ESC secret pack)
Workspace: Harbor Quay project desk as pasted
SpecNames: staging stack map as pasted; worker stack map as pasted. Uptime percents UNKNOWN.
StackCues: staging as pasted. production UNKNOWN.
ResourceCues: aws:s3:Bucket as pasted; aws:ec2:Instance as pasted. lambda UNKNOWN.
ProviderNotes: aws name only as pasted. Secret VALUES NOT IN INPUTS.
Banned: guaranteed uptime, deploy invent, replica invent, secret invent
Never: invent deploy counts, invent replica sizes, invent uptime percents, invent billing secrets
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: stack Harbor Quay staging as pasted resource cue aws:s3:Bucket as pasted provider notes aws name only as pasted; stack River Ops staging as pasted resource cue aws:ec2:Instance as pasted. Deploy invent NONE. Replica invent NONE. Version Pulumi 3 as pasted. Workspace Harbor Quay project desk. SpecNames staging stack map as pasted; worker stack map as pasted. Uptime percents UNKNOWN. StackCues staging as pasted. production UNKNOWN. ResourceCues aws:s3:Bucket as pasted; aws:ec2:Instance as pasted. lambda UNKNOWN. ProviderNotes aws name only as pasted. Secret VALUES NOT IN INPUTS. Lang English. Banner: not a Pulumi brand-kit generator; not an SLA guarantee. Forbidden: invented deploy counts, replica sizes, uptime percents, billing secrets, guaranteed uptime, deploy invent, replica invent, secret invent.

2. Stack resource map.
1. Harbor Quay staging | StackCues staging as pasted | ResourceCues aws:s3:Bucket as pasted | ProviderNotes aws name only as pasted | deploy VALUES NONE | replica NONE | Pulumi stack resource map only.
2. River Ops staging | StackCues staging as pasted | ResourceCues aws:ec2:Instance as pasted | ProviderNotes beyond aws name NOT IN INPUTS | deploy VALUES NONE | replica NONE.
Uptime percents UNKNOWN so write uptime-percent VALUES NOT IN INPUTS. production not invented beyond StackCues.

3. Spec name set. staging stack map as pasted; worker stack map as pasted as SpecNames. Unnamed rows NOT IN INPUTS. Never invent uptime-percent VALUES.

4. Version lock. Pulumi 3 as pasted as pasted. Refuse unreleased ESC secret pack.

5. Refuse list. inventing deploy counts; inventing replica sizes; inventing uptime percents; inventing billing secrets.

6. Compliance. Quoted Banned: guaranteed uptime, deploy invent, replica invent, secret invent. Cut. Quoted Never: invent deploy counts, invent replica sizes, invent uptime percents, invent billing secrets. Cut. Format ledger + table + specs + version + refuse + compliance.

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...