Guides

Terraform ने Dev, Stage आणि Prod कसे व्यवस्थापित करावे

By Ravindra Bagale, DevOps trainer · LinkedIn · Published: 28 October 2026 · Last updated: 28 October 2026

Shared modules, प्रति env state key + tfvars, -var-file plan, prod फक्त CI+approve.

Language: English · मराठी · हिंदी

वेगळे state का

एक state = मिश्र blast.

Why: dev destroy ≠ prod. What: key per env. How: apply आधी नाव.

Example 1: Folder layout

Type this:

mkdir -p /tmp/tfenvironments/{dev,stage,prod} /tmp/tfenvironments/modules && printf '%s\n' 'dev/' 'stage/' 'prod/' 'modules/' > /tmp/tfenvironments/layout.txt && cat /tmp/tfenvironments/layout.txt

You will see:

dev/
stage/
prod/
modules/

What it means: Each env folder has its own state backend key.

Example 2: Dev tfvars

Type this:

printf '%s\n' 'env = "dev"' 'instance_type = "t3.micro"' 'cidr = "10.0.0.0/16"' > /tmp/tfenvironments/dev/dev.tfvars && cat /tmp/tfenvironments/dev/dev.tfvars

You will see:

env = "dev"

What it means: Small sizes in dev — save INR on labs.

Example 3: Prod tfvars

Type this:

printf '%s\n' 'env = "prod"' 'instance_type = "t3.large"' 'cidr = "10.20.0.0/16"' > /tmp/tfenvironments/prod/prod.tfvars && cat /tmp/tfenvironments/prod/prod.tfvars

You will see:

env = "prod"

What it means: Different CIDR avoids overlapping VPN routes.

Concept 1: tfvars/keys

वेगळे sizes/CIDR.

Why: ambient गोंधळ. What: -var-file; keys. How: backend तपासा.

Example 4: Backend key per env

Type this:

printf '%s\n' 'key = "prod/network/terraform.tfstate"'

You will see:

key = "prod/network/terraform.tfstate"

What it means: Never share one state file across env names.

Example 5: Plan with var-file

Type this:

printf '%s\n' 'terraform plan -var-file=dev.tfvars'

You will see:

terraform plan -var-file=dev.tfvars

What it means: Explicit file beats ambient env vars for clarity.

Example 8: Check which state

Type this:

printf '%s\n' 'terraform workspace show; head -5 backend.tf'

You will see:

terraform workspace show; head -5 backend.tf

What it means: Say the env name out loud before apply.

Concept 2: Prod guard

CI+approve.

Why: laptop prod = incident. What: approval; ticket destroy. How: workspaces optional.

Example 6: Workspace alternative

Type this:

printf '%s\n' 'terraform workspace select dev || terraform workspace new dev'

You will see:

terraform workspace select dev || terraform workspace new dev

What it means: Workspaces share code; many teams still prefer folders.

Example 7: Protect prod apply

Type this:

printf '%s\n' 'ok: prod apply only from CI with approval gate'

You will see:

ok: prod apply only from CI with approval gate

What it means: Laptop prod apply is how Friday outages start.

Example 12: Destroy only non-prod casually

Type this:

printf '%s\n' 'terraform destroy -var-file=dev.tfvars  # never muscle-memory this on prod'

You will see:

terraform destroy -var-file=dev.tfvars  # never muscle-memory this on prod

What it means: Prod destroy needs a ticket and two humans.

Concept 3: Promote/tags

stage rehearsal; cost tags.

Why: untagged bill. What: same module ver. How: promote.

Example 9: Shared modules path

Type this:

printf '%s\n' 'source = "../../modules/vpc"'

You will see:

source = "../../modules/vpc"

What it means: One modules tree; three env callers.

Example 10: Tag everything

Type this:

printf '%s\n' 'tags = { Environment = var.env, Owner = "payments" }'

You will see:

tags = { Environment = var.env, Owner = "payments" }

What it means: Cost explorer filters by Environment tag.

Example 11: Drift between envs

Type this:

printf '%s\n' 'Same module version in stage and prod; promote intentionally'

You will see:

Same module version in stage and prod; promote intentionally

What it means: Stage is the dress rehearsal.

Env card

1 folders 2 keys 3 tfvars 4 modules 5 CI prod 6 tags

Suppose: wrong env

Stop; check key.

Suppose: CIDR clash

Separate CIDRs.

Check yourself (quiz)

modules → per-env state → tfvars → plan → guarded apply. Did you understand? Let us try it once more.