chore: make playbooks available for Ansible Galaxy installs #658
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
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.
Proposed Changes
By moving the three playbooks
reboot,resetandsiteinto the subdirplaybooks, they become available when installing the collection via Ansible Galaxy. The README references how we can then use them.As a side note, dependencies still have to be installed manually. Only when we actually build/package the collection and publish it to Ansible Galaxy, it would include the dependencies.
Tihs PR addresses issue #657. We might then think whether we also want to release this collection on the Ansible Galaxy platform.
Checklist
site.ymlplaybookreset.ymlplaybookRunning the tests locally fails due to network restrictions. Let's rely on CI testing. 🙈