Historique | Voir | Annoter | Télécharger (1,33 ko)
fix #143 - properly escape rulename for interfaces
remove duplicate expect
this is handled by the next - more specific - expect anyways
Make sure that the list of interfaces is mocked
If 'networking' is not removed from the facts, the values declared in`default_module_facts.yml` win (the fact set contains two keys:`:networking` and `'networking'`)
This test has always been wrong as the interfaces were never been...
rubocop:auto_correct results
Pet rubocop
Do not test nftables::rules repeatadly
Rather than testing the contents of nftable::rules just testthat nftables::rules instance is correct.
The existing test for the define nftables::rules is enough.
Motivation here is to make changes to nftables::rules easier to handle...
Reload rules atomically
Background: The unit file for nftables on CentOS 8 contains:
```ExecStart=/sbin/nft -f /etc/sysconfig/nftables.confExecReload=/sbin/nft 'flush ruleset; include "/etc/sysconfig/nftables.conf";'ExecStop=/sbin/nft flush ruleset```...
Switch $order$fragmenta/b to $order-$fragment-a/b
Add comments for all the nftable::rules entries
For each nftable::rule this adds an extra concat fragment toadd a comment containing the name and order number for the rule.
The motivation here is to make the mapping from resulting rules backto puppet code more obvious. When adding a new rule it should be more...
Add class bridges
Allow traffic from any bridge to itself by default
