Infrastructure as Code Review
Published · Updated
Catch the resource that quietly gets destroyed on next apply.
Tags: Engineering, Technical, Research
Prompt template
``` [textarea: Paste the configuration] ``` Tool: [dropdown: Terraform, Pulumi, CloudFormation, CDK, Bicep, Ansible] Provider and services: [text: Cloud and what it provisions] Environments: [textarea: How dev, staging and production are separated] State: [textarea: Where it lives and who can apply] People who apply changes: [text: How many] Start with anything that would be replaced rather than updated on the next apply, and anything destructive hiding in a plan nobody reads carefully. Then: secrets handling and whether sensitive values land in state. Module structure and environment separation. Hardcoded values that should be variables. Finish with the review and approval process appropriate for a team of my size.