-
Notifications
You must be signed in to change notification settings - Fork 100
Introduce Ansible Module Collection guide #3859
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
base: master
Are you sure you want to change the base?
Introduce Ansible Module Collection guide #3859
Conversation
In #3844, I hinted at my intention to move the updated Ansible content to a separate guide. This is an idea that we discussed with @evgeni and @ekohl who both seemed to be in favor of it. The only actual new content is these files:
Both are very generic but still, @evgeni, can you please review them? |
guides/common/modules/ref_getting-help-with-project-ansible-module-collection.adoc
Outdated
Show resolved
Hide resolved
guides/common/assembly_introduction-to-project-ansible-module-collection.adoc
Outdated
Show resolved
Hide resolved
ac06401
to
3633825
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
two minor comments.
guides/common/assembly_example-playbooks-based-on-modules-from-project-ansible-collection.adoc
Outdated
Show resolved
Hide resolved
3633825
to
8b35a0e
Compare
triage: kindly requested a tech review from Evgeni. |
What changes are you introducing?
Moving the freshly updated docs on using the Ansible Module Collection (#3844) from the Admin guide to a separate guide.
Tweaking the "getting help" sections in the Hammer and API guides so that both these two and the new Ansible guide can follow the same structure.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
The Ansible Module Collection is a Project management tool that is in many ways equivalent to Hammer and API. The proposed Ansible guide's structure mirrors the structure of the existing Hammer and API guides to create an equivalent to them.
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
N/A
Checklists
Please cherry-pick my commits into: