Add the tomswallapi_policy resource #12

New Issue

2026-07-26T17:17:21+10:00

benvin commented

2026-07-26 17:17:21 +10:00

Problem. The provider covers zones, groups, portgroups, fabrics, devices,
bindings, rules, and the NAT tier — but not policy, the default zone→zone
posture from the DESIGN.md catalog. Default-drop is the foundation the rules
tier stands on; until policies are HCL-manageable, the define-once story has a
hole exactly where the security posture lives, and bootstrap requires
out-of-band API writes (which then drift from Terraform state).

Proposal. tomswallapi_policy with source, dest, action, log,
and priority (see #14). Sequence it ahead of further long-tail resources.

**Problem.** The provider covers zones, groups, portgroups, fabrics, devices, bindings, rules, and the NAT tier — but not `policy`, the default zone→zone posture from the DESIGN.md catalog. Default-drop is the foundation the rules tier stands on; until policies are HCL-manageable, the define-once story has a hole exactly where the security posture lives, and bootstrap requires out-of-band API writes (which then drift from Terraform state). **Proposal.** `tomswallapi_policy` with `source`, `dest`, `action`, `log`, and `priority` (see #14). Sequence it ahead of further long-tail resources.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: unkin/terraform-provider-tomswallapi#12

Add the tomswallapi_policy resource #12

Add the `tomswallapi_policy` resource #12