Make this a role

[kjgd]

This should be formatted as a Role so that it can be incorporated into other playbooks, by

cd my_playbook/roles
git pull [wireguard_ansible repository url]

I have the major changes done (moving things into tasks/ etc, renaming wireguard.yml to main.yml, etc).

However the issue remains how to create a playbook.yml that can live in the wireguard_ansible directory:

#
# Unfinished: As written this file needs to be placed in ../../ and the
# current directory in ../roles/, so e.g
#   - ~/my_playbook/playbook.yml
#   - ~/my_playbook/roles/wireguard_ansible/
#
# There is probably a way to include the files directly without the
# `roles` directory structure, while maintaining the ability to use
# the current directory as a role:
#   https://docs.ansible.com/ansible/2.3/playbooks_roles.html
#
- name: Setup VPN
  hosts: all
  gather_facts: true
  roles:
    - {role: 'wireguard_ansible', tags: 'wireguard'}

I've made quite a lot of other minor fixes as well:

• automatically turn off systemd-resolved if needed,
• make the playbook idempotent and only generate keys if the config files don't exist, don't nuke the keys on every run
• make rebooting the server a handler which only runs if it needs to be run,
• automatically detect the ipv4 interface name if it is not eth0,
• automatically fetch client config from the server

However, submitting pull requests for those is not practical unless we get the role-friendly directory structure solved, since my files have already been rearranged to fit the role structure.

(I also have to do some minor debugging and figure out why connections are not working, oops!)

[iamckn]

Let me look at the role structure this week then you can do a pull request for the other fixes. Thank you for the great suggestions and improvements!

[iamckn]

The project has been restructured as a role. The wireguard_role directory can easily be included in other playbooks.

The following have also been done:

• make rebooting the server a handler which only runs if it needs to be run,
• automatically detect the ipv4 interface name if it is not eth0,
• automatically fetch client config from the server

For the other suggested fixes, you can submit a pull request as is necessary.