Infrastructure as Code Repository Layout
Organise modules, environments and state sensibly.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Plan the layout of an infrastructure repository. Cloud provider: [CLOUD_PROVIDER]. Tool: [IAC_TOOL]. Environments: [ENVIRONMENTS]. Teams: [TEAMS]. Resources managed: [RESOURCES]. Propose folders for modules, environments, shared configuration and documentation. Define how state is stored and locked, how secrets are handled, naming conventions, tagging, and how changes are reviewed with a plan before apply. Describe how to avoid copy and paste between environments. Return a directory tree, rules for pull requests, a diagram described in text, and a checklist for starting a new environment. Mention the risks of drift and how to detect it with scheduled plan runs. Add a worked tree layout: modules for network, compute and storage; environments folders for development, staging and production, each with its own variable file and state; a shared folder for policies. Suggest a rule that production changes need a reviewed plan output attached to the pull request. Add a risk list: a mistake in a shared module can affect every environment, so version modules and roll out changes one environment at a time.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.