Keep existing IP assignments if none are provided #41
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mortenlj
added a commit
to mortenlj/ansible-role-zerotier
that referenced
this pull request
Mar 30, 2022
Lifted from m4rcu5nl#41
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Defaulting ipAssignments to [] will reset the IP assignments for the member each time the playbook runs if zerotier_member_ip_assignments is not set. If automatic IP assignment is enabled, ZeroTier will then automatically assign a new IP, but in my experience the new IP will not always be the same as the previous one. Omitting the ipAssignments list when we don't want to assign an IP manually seems to fix the issue.