chore(terraform): OVH prod tfvars for the migration (services d2-4, web d2-2) #197
Loading…
Reference in a new issue
No description provided.
Delete branch "jfraeys/chore/ovh-prod-tfvars-phase1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#187 phase 1 prep.
terraform/environments/ovh/prod.tfvars: web keepsinstance_type = d2-2(smallest OVH flavor, 2 GB);ovh_node_flavors = { services = "d2-4" }(2 vCPU, 4 GB, 50 GB, from the real BHS5 flavor list). Also pinsenable_desec_dns = falseandovh_backup_s3_username = ""for this workspace: the vault sets TF_VAR_enable_desec_dns=true and the OVH S3 IAM username, which would make the newovhworkspace's separate state try to create the deSEC zone and manage the S3 IAM policy that thelinodeworkspace already owns (the 2026-09-23 incident in docs/incidents.md was this class of overlap).tofu fmtalso realigned neighbouring lines.No apply. Provisioning is a separate, explicit step:
tofu workspace new ovh(creates its own empty state), then./setup --workspace ovh --confirm-prod --no-ansible --var-file terraform/environments/ovh/prod.tfvars; read the plan first: expect 2 instances (web d2-2, services d2-4), 0 DNS resources, 0 IAM.🤖 Generated with Claude Code
https://claude.ai/code/session_01Ge5tovcwdEUBtPwUktsZZZ