Proposed Collection Structure

[artis3n]

Now that we have an Ansible Collection, using this issue to track the overall design conception for how roles, plugins, and other resources should be organized, as well as what roles, plugins, and other resources to create. Provide feedback on this issue as we develop the collection design. All names are up for modification until released into the collection.

plugins/
  |-- inventory/
        |-- (something to dynamically create your inventory from registered tailscale nodes)
  |-- lookup/
        |-- dns_query (perform a DNS query using the local DNS forwarder | "tailscale dns query" cli)
  |-- modules/
        |-- (series of modules to configure tailscale admin pane settings over API. Specific modules added below)
        |-- machine_info (retrieve information about machines in your tailscale environment)
roles/
  |-- configure_daemon (configure tailscaled on a server. | "tailscaled" cli)
  |-- configure_machine  (configure per-machine tailscale settings not available to tailscale up. | "tailscale set" cli)
  |-- funnel (configure tailscale funnel on a server. | "tailscale funnel cli")
  |-- generate_cert ("tailscale cert" cli)
  |-- machine  (install tailscale on a server. | "tailscale up" cli)

[artis3n]

In a v2 of this collection I might take artis3n.tailscale.machine and make it a module to query the tailscale API and make the "install tailscale onto a server" role something else, maybe artis3n.tailscale.install_machine? Will plan to keep backwards compatibility for now.