tomswallapi_device_config data source + rule fanout preview #11

Open
opened 2026-07-26 17:15:54 +10:00 by benvin · 0 comments
Owner

Problem. DESIGN.md §10 lists a rendered-config preview data source and a
"which devices does this intent touch" fanout preview surfaced in plan;
neither exists in the provider. For a firewall control plane, seeing the
concrete per-device delta before apply is the single most important safety
feature — the equivalent of reading shorewall's generated script before
restart. I'd rank this above adding further resource types.

Proposal.

  • data "tomswallapi_device_config" "fw_a" returning the rendered
    tomswall.yaml for a device at the current model state, so plan output
    diffs it.
  • Fanout: computed attribute on tomswallapi_rule listing enforcing devices,
    so plan shows blast radius.
**Problem.** DESIGN.md §10 lists a rendered-config preview data source and a "which devices does this intent touch" fanout preview surfaced in plan; neither exists in the provider. For a firewall control plane, seeing the concrete per-device delta *before* apply is the single most important safety feature — the equivalent of reading shorewall's generated script before `restart`. I'd rank this above adding further resource types. **Proposal.** - `data "tomswallapi_device_config" "fw_a"` returning the rendered `tomswall.yaml` for a device at the current model state, so plan output diffs it. - Fanout: computed attribute on `tomswallapi_rule` listing enforcing devices, so plan shows blast radius.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/terraform-provider-tomswallapi#11