Whitelist Contabo V92 + V76 (strong EU tiers) — current whitelist products all 'not available'

[izzywdev]

@claude — FuzeFront node provisioning (fuzefront-worker-2) is fully working end-to-end EXCEPT the product tier: the handler's terraform apply reaches Contabo instance-create, but every product ID currently in config/infra-request-whitelist.json (V1, V45, V46, V47) returns Bad Request Product <X> is not available in region EU. The whitelist holds stale/unavailable product IDs.

Ask: add V92 and V76 to allowed_product_ids in config/infra-request-whitelist.json. Both are valid EU Cloud VPS products per Contabo's official Terraform provider examples; V92 ≈ 8 vCPU / 30 GB is the tier FuzeFront actually needs (the smaller whitelisted ones weren't strong enough anyway).

Before finalizing, confirm availability with cntb (availability is account/region-specific): e.g. cntb get products / the create-instance product list, since even V47 etc. were 'not available'. Then let FuzeFront know which tier(s) are actually orderable so node-requests.json can pin the right one. (Today FuzeFront's deploy/terraform/node-requests.json = V92.)

Note: a gated PR is likely already open from FuzeFront's latest dispatch (V92 isn't whitelisted yet → the handler routes it to a gated terraform plan for manual approval). Whitelisting V92 makes it auto-apply instead.

STATE (FuzeFront side, done): deploy/terraform now (1) wires the contabo-k3s-node module's required args (contabo creds + k3s join), (2) declares an S3 remote backend (backend "s3" {}) so node state is cloud-persisted via your handler's -backend-config (no more local/ephemeral CI state). Acceptance: V92 (+V76) in allowed_product_ids, cntb-confirmed available, fuzefront-worker-2 provisions + joins.

[claude]

Claude finished @izzywdev's task in 1m 30s —— View job • claude/issue-65-20260624-2109 • Create PR ➔

---

Whitelist Contabo V92 + V76 ✅

• Read config/infra-request-whitelist.json
• Add V92 and V76 to allowed_product_ids
• Validate change & commit/push
• ⚠️ Confirm availability with cntb — could not run in this CI runner (see below)

What changed

config/infra-request-whitelist.json → allowed_product_ids now:

["V1", "V45", "V46", "V47", "V76", "V92"]

I added V92 and V76 rather than replacing the existing IDs — the validator (scripts-tools/validate_infra_request.py) only checks membership, so a V92 node request will now match the whitelist and auto-apply instead of routing to a gated terraform plan PR. If you'd prefer to also prune the stale/unavailable V1/V45/V46/V47, say the word and I'll drop them.

⚠️ Availability NOT confirmed via cntb

I was unable to run cntb here — the CLI isn't installed on this Actions runner and no Contabo API credentials (CNTB_* / CONTABO_CLIENT_ID...) are available to me. Since availability is account/region-specific (V47 etc. were whitelisted yet returned Product not available), please confirm before relying on auto-apply:

# list all products visible to your account
cntb get products

# or the create-instance product list (what apply actually checks)
cntb get products --output json | grep -iE 'V92|V76'

If a tier shows not available for region EU, whitelisting it won't help — the Contabo instance-create will still 400. V92/V76 come from Contabo's official Terraform provider examples, but that's not a guarantee for your account/region.

Back to FuzeFront

• Whitelist now permits V92 (and V76), so the gated PR from the latest dispatch should auto-apply once merged — assuming cntb confirms V92 is orderable in EU.
• Action for you: run the cntb get products check above and pin deploy/terraform/node-requests.json to whichever of V92/V76 is actually orderable. The handler's whitelist now accepts either.

• claude/issue-65-20260624-2109