summaryrefslogtreecommitdiffstats
path: root/roles/wireguard
AgeCommit message (Collapse)AuthorFilesLines
2026-03-04Remove duplicate fields from argument_specs filesAhmed Abdelhalim1-6/+0
2026-02-21Fix bash dependencies in shell scripts calledAhmed Abdelhalim1-0/+1
2026-01-24Fix ansible 2.20.1 deprecation warning about ansible_varsAhmed Abdelhalim1-1/+1
2025-12-16Remove company from the roles metaAhmed Abdelhalim1-1/+0
2025-11-24Add the sed role dependency for completenessAhmed Abdelhalim1-0/+1
2025-11-14Fix example config, and ignore rpi idempotent test failureAhmed Abdelhalim1-0/+6
The reason the idempotent test fails is the following: - 1st run: wireguard role deploys all the configured VPN connections - 1st run: wg_portal updates the file permissions /etc/wireguard (ACLs) - 2nd run: wireguard sees the file changed, deploys again (idempotent failure)
2025-11-13Minor fixes to autostart connection validation/service logicAhmed Abdelhalim1-6/+15
2025-11-13Add mechanism to clean up wireguard configurationsAhmed Abdelhalim1-7/+27
When a wireguard configuration gets removed from the group/host variables, the role now removes them and make sure only the files found in the vars are the ones to be configured on the hosts
2025-11-03Remove unneeded backup of files in wireguardAhmed Abdelhalim1-1/+0
2025-10-22Refactor naming of packages and services to follow same conventionsAhmed Abdelhalim3-3/+3
2025-09-20Migrate to the new loop syntaxAhmed Abdelhalim1-3/+3
2025-09-14Fix wireguard stopping vpn when it's not necessaryAhmed Abdelhalim1-1/+1
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)
2025-09-14Put back the idempotent ignore testAhmed Abdelhalim1-0/+2
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.
2025-09-13Remove the idempotence ignore test in wireguardAhmed Abdelhalim1-2/+0
Since the ACL fix probably fixed this one too
2025-09-12Fix idempotence for wg-portal roleAhmed Abdelhalim1-9/+2
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!
2025-09-12Fix looping over wireguard connection dictAhmed Abdelhalim1-1/+1
2025-09-10Follow the ansible recommendation of using systemd_serviceAhmed Abdelhalim1-2/+2
2025-09-10Refactor role dependencies to be more module modularAhmed Abdelhalim1-2/+2
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.
2025-08-31Add wireguard role readmeAhmed Abdelhalim1-0/+53
2025-08-21Fix the wireguard installAhmed Abdelhalim2-2/+1
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
2025-08-21Add wireguard role and fix testingAhmed Abdelhalim6-0/+102
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).