Caught live on omantel.biz re-provision (deploymentId ab0bf689620f4102):
tofu plan failed at exit 1 with:
Error: Invalid value for variable
on variables.tf line 296:
296: variable "domain_mode" {
├────────────────
│ var.domain_mode is "byo-manual"
Domain mode must be 'pool' or 'byo'.
The wizard's StepDomain has three options (pool / byo-manual /
byo-api) so the UX can branch the operator into the right flow:
- pool: OpenOva owns the parent zone via Dynadot+PDM
- byo-manual: operator pastes NS records into their registrar
- byo-api: operator's registrar API drives NS automatically
The OpenTofu module's `variable "domain_mode"` validation only
accepts the binary pool/byo distinction — from the cloud-infra layer
(Hetzner servers, network, LB) NONE of those wizard distinctions
matter; tofu only needs to know whether to call Dynadot at apply
time. The three-mode wizard value was being written verbatim to the
tfvars without mapping.
Add `mapDomainModeForTofu(wizardMode)` helper:
- "pool" → "pool"
- "byo-manual"→ "byo"
- "byo-api" → "byo"
- empty → "byo" (test path that doesn't set the field)
Bump chart 1.4.83 → 1.4.84.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
25f14469d3