4.2.0

Changed

• Refactored all tests that run in CI to support testing against Headscale instead of only against Tailscale (#319) Thanks @mprasil !
• Refactored how state idempotency is tracked. State is now simpler to manage inside the role and a situation in which the role would see state as already configured and fail to properly invoke tailscale up is now fixed. (#320) Thanks @mprasil !
• As a result of the prior change, if any error occurs wherein executing tailscale up fails, the role will clear its state so that re-running the role will always run tailscale up and re-save the state. The tailscale up command is idempotent if all passed parameters remain the same, so this change will not break users, but may fix some erroneous failures to re-run tailscale up in some edge cases.
• Updated dependencies

Added

• Added a subtle note about how to use this role with Headscale to the README

New Contributors

• @mprasil made their first contribution in #320

4.1.0

Added

• Added support for Amazon Linux 2023 as a target host

Changed

• The CI suite is now upgraded to ubuntu 22.04 runners and leverages a reusable workflow to continue functioning with some legacy OS's that don't like cgroups v2 on an ubuntu 22.04 host. Doesn't matter for users of this role, but I'm glad to finally have a resolution there.

4.0.0

Added

• BREAKING CHANGE: This role now adheres to https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html and stores state in $XDG_STATE_HOME/artis3n-tailscale, or $HOME/.local/state/artis3n-tailscale if that env var is not present. This is technically a breaking change as this role will report state as "changed" upon the next run even if no state has changed. After the first time in which the state migrates to this new location, the role will correctly report state idempotency again. #286

Removed

• The legacy state directory, $HOME/.artis3n-tailscale will be removed from target machines the next time this role is run.

Fixed

• The CI suite experienced frequent timeouts from Ansible Galaxy. This is a known problem due to regular load against the Galaxy servers with no clear solution from Ansible. This role now bypasses Ansible Galaxy to install the community.general collection directory from its Git URL. This has no impact on end users, but contributors to this role should no longer experience failing tests due to Galaxy timeouts.

Changed

• BREAKING CHANGE: The vars/main.yml variables have all been updated with a prefix to help prevent conflicting with other role's parameters. These variables are not intended to be modified by end users, but if any end users are modifying these variables, they will need to update their references. #284 Thanks @hollow !
• Updated dependencies

New Contributors

• @hollow made their first contribution in #284

3.5.0

Added

• Adds support for OpenSUSE Tumbleweed and Leap (#256 and #268). Thanks @Jamdoog !
• Uses of apt update now set a cache expiration of one hour, to prevent this role from triggering false idempotency failures (#278). Thanks @mnaser for the PR and @dgibbs64 for raising!

Fixed

• Fixed an error incorrectly processing the ansible_distribution_major_version of pre-release Debian distros (#259)
• Conditional checks in this role would improperly fail if the role had previously installed Tailscale but the authkey had since expired. They will now correctly succeed (#280). Thanks to @toadjaune for raising.

Changed

• Updated dependencies

New Contributors

• @Jamdoog made their first contribution in #256
• @mnaser made their first contribution in #278

3.4.0

Fixed

• Ubuntu and Debian distros now store (and remove) the Tailscale GPG key in /usr/share/keyrings instead of using the legacy apt-key tool, which is deprecated in Ubuntu 22.04. This is backwards-compatible with earlier Ubuntu/Debian-based distributions. #249 Thanks @wormi4ok !

Changed

• Ansible-lint in the CI pipeline now pins to the production rules profile in ansible-lint's new format.

New Contributors

• @wormi4ok made their first contribution in #249

3.3.0

Adds

• Adds a latest state, making the possible state parameter values latest, present, or absent. #239

This role uses latest by default to help ensure your software remains up-to-date and incorporates the latest security and product features. For users who desire more control over configuration drift, present will not update Tailscale if it is already installed. Changes to tailscale_args will be applied under both latest and present; this parameter only impacts the version of Tailscale installed to the target system.

Changed

• Updated dependencies

3.2.3

Changes

• Updates dependencies

3.2.2

Fixes

• Restructures the order of tailscale up arguments such that errors are clearly funneled up instead of masked behind an invalid auth key message. Thanks @panos-- ! #206

Adds

• Adds a unit test to catch a future regression of the tailscale up argument formatting. Thanks @panos-- ! #206

3.2.1

Fixes

• Fixes the tailscale up command which in 3.2.0 incorrectly quoted multiple flag arguments, resulting in a command-line failure of the ansible.builtin.command module. Thanks @h3poteto ! #204

3.2.0

Added

• Support for Ubuntu 22.04
• Support for Debian 12 (Bookworm)