Run the home node's names through the module and the policy, not only naming.py #13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Why
decisions/2026-10-29-home-node-inventory-arbitrations.mdsection 5 records it: onlytools/naming.pywas run on the home node's names. The module (modules/naming) and the policy (policy/naming.rego) were not.v4.0.0 implements
reserved_namesthree times, in the tool, the module and the policy. Mutations proved each one on its own cases. Nothing yet confronts the three on the estate's real names. A divergence would surface at the home node's first plan, on names that are final.Example
The ipset
managementonproxmox_virtual_environment_firewall_ipsetis accepted bynaming.py. That the module lets it through for aper-shr-plt-...call is not shown by any test running on the inventory.Done when
The inventory of section 6.2 (26 types) feeds a fixture read by all three engines, and
make checkfails when any of them disagrees with the others.Filed for a later grouped pass over the kit's open tickets.