| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
It's only necessary to stop the VPN to set another one running instead
(as the configurations are not built to stack VPN although possible)
|
|
The idempotent test is only failing on the second run,
the reason is, on the first run the wireguard files are created with
default permissions, then the wg_portal role update the ACL.
On the second run, the wireguard role recognizes the difference in the
permissions, and update the files (expectedly), the default ACL then
takes place and set the permissions correctly with ACLs
On any successive run, the role is idempotent and doesn't update the
files again.
|
|
Since the ACL fix probably fixed this one too
|
|
Delegate the /etc/wireguard directory creation to the package, this way,
if later the wg-portal role was to be installed and update that
directory ACL, it won't fail idempotent test.
Ignore the wireguard configuration creation, for some reason the usage
of dictionary is not preventing the detection of when items change!
|
|
|
|
|
|
This modularity means that each role can be installed in a playbook by
itself as long as the other roles exist around it.
This also straps the ensure dependency packages exist in any of the
roles tasks, they should be moved to their own roles and configured
properly if needed.
|
|
|
|
The conflict was due to resolvconf was removing the systemd-resolved
configuration and that was causing the network to go down and the
fallback on the statically managed resolv.conf (which wasn't able to
resolve the DNS) due to how network manager requiring the DNS resolution
to happen through systemd-resolved
|
|
The testing was failing because the use of the example files with the
same domain names, resulted in the files and the molecule variable were
being merged and therefore running tasks that would fail on test
(example, setting a fake VPN connection that wouldn't start).
|
