Replies: 3 comments 5 replies
-
Writing that out, I'm now partial to |
Beta Was this translation helpful? Give feedback.
-
I'm hoping I can find a way around it, but I may not be able to use |
Beta Was this translation helpful? Give feedback.
-
Ok still fleshing things out a bit but this should be equivalent to this current role, just migrated into https://github.com/artis3n/ansible-collection-tailscale https://galaxy.ansible.com/ui/repo/published/artis3n/tailscale/ ansible-galaxy collection install artis3n.tailscale |
Beta Was this translation helpful? Give feedback.
-
I am in the process of migrating this role into an
artis3n.tailscale
collection. The collection will host other roles and plugins, etc. in the future around interacting with Tailscale. Some commonly requested things would be modules and roles to interact with Tailscale's management API. This role is specific to creating and managing Tailscale nodes.This role will become
artis3n.tailscale.NAME
. What should name be?One option, since this role manages nodes in your tailnet, is to call it
ansible.tailscale.node
. Tailscale also uses "machines" and "devices" to refer to the things connected to your tailnet. Should we use one of those terms instead? Should it just benode
(ormachines
, ordevices
), orartis3n.tailscale.manage_nodes
, etc.? Some other format?Beta Was this translation helpful? Give feedback.
All reactions