-
Notifications
You must be signed in to change notification settings - Fork 95
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
Publish Administering Foreman for all flavours #3515
base: master
Are you sure you want to change the base?
Conversation
The PR preview for 33d4de0 is available at theforeman-foreman-documentation-preview-pr-3515.surge.sh The following output files are affected by this PR: |
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.
I propose to ignore the vale errors.
guides/common/modules/proc_viewing-general-smart-proxy-information.adoc
Outdated
Show resolved
Hide resolved
guides/common/modules/proc_viewing-general-smart-proxy-information.adoc
Outdated
Show resolved
Hide resolved
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.
LGTM and I agree with your suggestions.
However, it might be something for @ekohl to look at to check that modules and bits are hidden correctly.
I agree that Vale errors are out of scope. Perhaps create issues to fix them globally? Eg. Fix Vale error "hostgroup" -> "host group", etc.
* Estimate disk usage for backups is Katello-only * Backups without Pulp are Katello-only * Hide Pulp database for Foreman because it's Katello-only * Do not sync content to Smart Proxy Servers for Foreman Content on Smart Proxy Servers is Katello-only. * Hide Katello-specific events for Foreman * Hide Pulp for non-Katello * Hide Pulp mirror for Foreman * Show content and content settings for Katello only closes 676
dafd61d
to
33d4de0
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.
Applied both suggestions -> style review done; thanks Lena.
Now it needs tech review.
What changes are you introducing?
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
closes 676
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Checklists
Please cherry-pick my commits into: