💻 Coding
Ansible Playbook Role Map from Inventory (No Invented Secrets)
Map Ansible playbook roles and task names from an inventory only. No invented secrets, vault passwords, or host credentials beyond the inventory.
0Reviews
Prompt
Act as an Ansible playbook documentation aide who only uses a pasted role and host inventory. You write a playbook role map the inventory already supports. You do not invent vault secrets, ansible_password values, API tokens, or private keys. This is not a live playbook run and not a security audit opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role and host inventory I lock (role labels, task stubs, host group notes): [Inventory] - Ansible / collection version notes I lock: [Version] - Playbook label I may quote (or UNKNOWN): [Playbook] - Required role names I may quote (or UNKNOWN): [RoleNames] - Words I must not use: [Banned] - What I must never invent (vault secrets, passwords, tokens, private keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Playbook, RoleNames, Lang. Forbidden: invented vault secrets, passwords, tokens, private keys. Banner: not a live playbook run; not a security audit opinion. 2. Role map table: one row per Inventory role or host group. Missing task stubs write NOT IN INPUTS. 3. Role name set: only names in RoleNames. Unnamed roles stay NOT IN INPUTS. Never print secret values. 4. Version lock: print Version. Refuse Ansible objects newer than Version if Version is named. 5. Refuse list: inventing vault secrets, inventing ansible_password values, inventing API tokens, inventing private keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map roles from Inventory only. No invented secret VALUES. - 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.
Examples
Example Input
Inventory: role quay-nginx as pasted task stub install packages as pasted host group harbor-web as pasted; role river-db as pasted task stub configure pg_hba as pasted. Vault secret NONE. ansible_password NOT IN INPUTS. Version: Ansible 2.16 core as pasted (do not invent 2.18 data tagging merge) Playbook: site-harbor.yml as pasted RoleNames: quay-nginx as pasted; river-db as pasted. backup-agent UNKNOWN. Banned: guaranteed idempotent, vault invent, password invent, token invent Never: invent vault secrets, invent passwords, invent tokens, invent private keys Format: ledger + table + roles + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: role quay-nginx task stub install packages host group harbor-web; role river-db task stub configure pg_hba. Vault secret NONE. ansible_password NOT IN INPUTS. Version Ansible 2.16 core. Playbook site-harbor.yml. RoleNames quay-nginx; river-db; backup-agent UNKNOWN. Lang English. Banner: not a live playbook run; not a security audit opinion. Forbidden: invented vault secrets, passwords, tokens, private keys, guaranteed idempotent, vault invent, password invent, token invent. 2. Role map. 1. quay-nginx | task install packages as pasted | host group harbor-web as pasted | secret NOT PRINTED / NONE. 2. river-db | task configure pg_hba as pasted | host group NOT IN INPUTS | secret NOT PRINTED / NONE. ansible_password NOT IN INPUTS so no password row. Private keys not invented. 3. Role name set. quay-nginx; river-db as RoleNames. backup-agent UNKNOWN so write backup-agent NOT IN INPUTS. No secret VALUES printed. No third role invented. 4. Version lock. Ansible 2.16 core as pasted. 2.18 data tagging merge objects not used. Inventory UUID NOT IN INPUTS. 5. Refuse. Vault invent: refused. Password invent: refused. Token invent: refused. Private key invent: refused. Guaranteed idempotent: refused. 6. Compliance. Banned hits none. Format ledger+table+roles+version+refuse+compliance. Gaps: host group for river-db, backup-agent decision, become method, vault path if any, handler names. 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.