Back to Discover

#variable map

2 prompts found

Terraform Module Variable Map from HCL Inventory (No Invented Secrets)
💻 Coding

Terraform Module Variable Map from HCL Inventory (No Invented Secrets)

Ppromptstudio·Sep 7, 2026
No rating

Map Terraform module variables from an HCL inventory only. No invented secrets, remote state paths, or account IDs beyond the inventory.

Act as a Terraform module variable mapper who only uses a pasted HCL inventory. You write a variable map the inventory already supports. You do not invent secret values, remote state paths, AWS account IDs, or provider tokens. This is not a terraform apply and not a cost estimate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - HCL inventory I lock (variable names, types, default notes): [Inventory] - Terraform / provider version notes I lock: [Version] - Module name I may quote (or UNKNOWN): [Module] - Required variables I may quote (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (secrets, state paths, account ids, tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Module, Required, Lang. Forbidden: invented secrets, state paths, account ids, tokens. Banner: not a terraform apply; not a cost estimate. 2. Variable map table: one row per Inventory variable. Missing types write NOT IN INPUTS. 3. Required set: only names in Required. Unnamed variables stay optional or NOT IN INPUTS. 4. Version lock: print Version. Refuse provider features newer than Version if Version is named. 5. Refuse list: inventing AKIA keys, inventing s3:// state paths, inventing 12-digit account IDs, inventing TF_VAR secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secrets or account IDs. - Honor Version. No emojis.

Terraform Module README from Variable Map (No Invented Providers) (Domain Pack)
💻 Coding

Terraform Module README from Variable Map (No Invented Providers) (Domain Pack)

Ppromptstudio·Sep 6, 2026
No rating

Write a Terraform module README from a locked variable map. No invented providers, versions, or example credentials.

Act as a Terraform module README writer who only uses a locked variable map. You write module README sections the inventory already supports. You do not invent default values, provider versions, secret literals, or resources not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Resource inventory I lock (resource types, names, notes): [VarsMap] - Variables map I lock (or NONE): [Vars] - Outputs map I lock (or NONE): [Outputs] - Providers I lock (or UNKNOWN): [Providers] - Example usage notes I lock (or NONE): [Example] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (defaults, providers, secrets, resources): [Never] - Output format: [Format] - Language: [Lang] Generate: 0. Terraform module README from variable map must list variables and providers only from Inputs. 1. Honesty ledger: Resources nouns, Vars, Outputs, Providers, Example, Cap, Lang. Forbidden: invented defaults, providers, secrets, resources. 2. README outline: at most Cap H2 sections. 3. Resources / Variables / Outputs tables: only inventory rows. Missing defaults write NOT IN INPUTS. 4. Providers and example: Providers and Example only; omit fake terraform block versions. 5. Refuse list: inventing default numbers, inventing provider versions if unnamed, inventing access key literals, inventing extra resources. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - README from Resources only. No invented defaults. - Honor Cap. No emojis.