-
Notifications
You must be signed in to change notification settings - Fork 96
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
Remove "Managing Foreman with Ansible" guide #3592
base: master
Are you sure you want to change the base?
Remove "Managing Foreman with Ansible" guide #3592
Conversation
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.
Technically I'd argue it's already shown for all flavors but this declares that we feel comfortable that it's ready for consumption.
Yes. The more I look at it, the more I think we don't need this tiny guide because it's already in https://docs.theforeman.org/nightly/Administering_Project/index-katello.html#Managing_Project_with_Ansible_Collections_admin |
+1 for removing it altogether |
+1 for removing it. (It seems pretty feature-based anyway, doesn't it?) |
875031d
to
b3032c7
Compare
TODO: after squashing and merging this PR, I have to open a PR against gh-pages to remove the built guide so that we do not end up with an outdated guide on docs.theforeman.org. |
What changes are you introducing?
Show Administering Foreman with Ansible guide for all builds
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Part of #396
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Alternative: we remove this guide because it is already part of https://docs.theforeman.org/nightly/Administering_Project/index-katello.html#managing-foreman-with-ansible
Checklists
no cherry-picks