Back to Discover

#terraform module readme

4 prompts found

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.

Terraform Module README from Variable Inventory (No Invented Providers) (Domain Pack)
๐Ÿ’ป Coding

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

PpromptstudioยทSep 6, 2026
No rating

Write a Terraform module README from a variable inventory. No invented providers, resources, or versions.

Act as a Terraform README author who only uses a locked variable inventory. 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): [VarInventory] - 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 inventory must document variables before providers 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.

Terraform Module README from Resource Inventory (No Invented Providers) (Domain Pack)
๐Ÿ’ป Coding

Terraform Module README from Resource Inventory (No Invented Providers) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Draft a Terraform module README from a resource inventory. No invented providers, versions, or resources.

Act as a Terraform docs engineer who only uses a locked resource inventory. 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): [Resources] - 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 resource inventory must lock providers and resources 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.

๐Ÿ’ป Coding

Terraform Module README and Examples Locked to Provider Version

PpromptstudioยทAug 25, 2026
No rating

Write a Terraform module README plus examples pinned to a named provider version. No invented resources, outputs, or newer provider APIs.

Act as a Terraform module maintainer writing README and examples for Terraform 1.9.x. You document only resources, variables, and outputs in Inputs. You lock the provider version they name. You do not invent cloud resources, and you do not use provider APIs newer than the pin. You work only from Inputs. You do not invent stats, citations, quotes, URLs, names, or records that are not in Inputs. Inputs: - Module name and source path: [Module] - Terraform version constraint: [TfVer] - Provider name and exact version pin: [Provider] - Variables with type, default, and description: [Vars] - Resources the module actually creates: [Resources] - Outputs with names and descriptions: [Outputs] - Required IAM or cloud permissions I can prove: [Perms] - Example call sites I allow (count): [Examples] - Known limitations: [Limits] - Words I must not use: [Banned] Generate: 1. Version lock: quote TfVer and Provider. List APIs you refuse because they are newer than the pin. 2. README title, short description, and a requirements table (Terraform, provider, pin). 3. Usage example: a complete module block using only Vars. No extra arguments. 4. Inputs table and Outputs table from Vars and Outputs only. Mark missing descriptions as NOT IN INPUTS. 5. Resources section: one line per item in Resources. Do not add a data source that was not listed. 6. Examples folder sketch: filenames and what each example proves, count limited to Examples. 7. Limitations and upgrade notes from Limits only. 8. Compliance pass: quote Banned words, invented resources, or unpinned latest. Cut them. Constraints: - HashiCorp Terraform 1.9.x language. Do not write OpenTofu-only features unless Inputs say OpenTofu. - Provider version is a pin, not a range you widen. - Never invent an output, variable, or resource address. - Do not paste fake terraform plan output or invented apply times. - Examples must apply with only the listed Vars.