fix(setup): each provider workspace uses its own tfvars by default #199
Loading…
Reference in a new issue
No description provided.
Delete branch "jfraeys/fix/workspace-default-var-file"
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?
Region, instance type and image are provider-specific, but lived in the vault as TF_VAR_region/_instance_type/_image (Linode values, equal to the root variable defaults) and as defaults. An OVH plan that lost its var-file then asked OVH for
ca-central:No suitable endpoint could be found in the service catalog(seen live 2026-10-15)../setupnow passes the workspace's own tfvars by default (default_var_file: linode -> linode/prod.tfvars (new), ovh -> ovh/prod.tfvars, ovh-dr -> ovh/dr.tfvars, linode-dr -> linode/dr.tfvars once copied from the example), also on passthrough plan/apply/destroy/import/console/refresh viawith_var_file; an explicit--var-fileor-var-filewins; staging workspaces are unchanged..env.exampledrops the instance type and image lines. Test: scripts/tests/test-setup-var-file.sh (in lint.yml).After merge, the operator removes the three redundant vault keys:
vault-set.py delete TF_VAR_region TF_VAR_instance_type TF_VAR_image(one at a time), then vault-pr.🤖 Generated with Claude Code
https://claude.ai/code/session_01Ge5tovcwdEUBtPwUktsZZZ