add migration message, upgrading min ansible requirement to 2.18 #540
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a
WARNINGat end of role execution about the new collection, https://github.com/artis3n/ansible-collection-tailscale.The only real option to do that with ansible is the
metamodule, and the only module option prior to ansible-core 2.18 isend_play. But I didn't want this role forcing the end of an end user's playbook. So this PR also sets the minimum Ansible requirement for to 2.18, which is when theend_roleoption formetawas added. This ends the current role only.This will be released as a major version bump, as ansible-core 2.18 is only available in
ansible11.x.