-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Support setting custom IP addresses #419
Comments
This works today following the node attribute configuration of that blog post - set a What alternate behavior/use case are you looking for from this role? |
Interesting! Didn't know about this before. I'd like to assign a static IP address to each machine. I guess I could use IP pools of I was hoping that this role can take in a static IP and call the |
Hmm, yeah I would put this under the (growing) use cases of admin console API calls which are out of scope of this role, but suggest I should probably get around to converting this role into a collection and adding roles and plugins into the collection for these API use cases. This role I want to keep focused on behavior that can be configured on a node itself (e.g. the CLI). |
Working on creating this collection - what should this role be called under that change? #529 |
Is your feature request related to a problem? Please describe.
The IP address of devices are auto-generated when using
tailscale up
. This makes it difficult to achieve infrastructure-as-code.Describe the solution you'd like
Tailscale allows us to specify custom IP addresses (blog post, api endpoint). It would be awesome if this Ansible role can support this.
Describe alternatives you've considered
Using this role for
tailscale up
, then using a custom script to set the IP via the API.Additional context
N/A
The text was updated successfully, but these errors were encountered: