Skip to content
DECLARE OR DRIFT

terminal-native infrastructure field manual

DECLARE OR DRIFT

Infrastructure as Code for terminal-native engineers building Azure, Cloudflare, Terraform, and Bicep workflows.

Start with IaC mental models Jump to Terraform on Azure Open command palette
resource_group
remote_state
managed_identity
key_vault
container_app
graph says: order is policy
terraform plan excerpt
+ azurerm_container_app.api
~ cloudflare_record.www ttl: 1 -> 300
- random portal change: unmanaged
+ module.identity.azurerm_user_assigned_identity.agent
Plan: 3 to add, 1 to change, 1 to destroy.

Fast index

Start with a chapter or search the guide.

Use `/` to focus the command nav, `j` and `k` to move through major sections, or jump directly into Terraform, Azure, Cloudflare, Bicep, patterns, and labs.

IaC mental models Terraform core Azure workflow Production patterns

Curriculum Map

01 open

IaC Mental Models
02 open

Terraform Fundamentals
03 open

Terraform on Azure
04 open

Terraform on Cloudflare
05 open

Bicep for Azure
06 open

Production Patterns
operator loop readonly 
terraform plan -out=tf.plan
terraform show -json tf.plan | jq '.resource_changes[].change.actions'
az deployment group what-if --resource-group core-prod
wrangler deploy --dry-run

Plan review

A plan shows the infrastructure change before it happens. Read it the way you read a database migration.

Default rules

Keep state small, name inputs clearly, store secrets outside the repo, and make CI print the plan before production apply.