Combine insights modules into one procedure module#3933
Combine insights modules into one procedure module#3933Lennonka merged 18 commits intotheforeman:masterfrom
Conversation
|
The PR preview for 3012099 is available at theforeman-foreman-documentation-preview-pr-3933.surge.sh The following output files are affected by this PR: |
|
Hi @AkshayGadhaveRH, the issue with how we document integration with Insights runs a bit deeper now and #3910 is there to address it. I'm not sure what to do and you are free to continue with your PR, just note that if my PR ends up being merged, I might end up overwriting your changes again. |
|
Hey @aneta-petrova I think your PR addresses a lot of issues with the insights modules. However, I feel we can still combine the two modules, once your changes are merged. |
|
Okay, Akshay! :) I'll do my best to get my PR done as quickly as possible so that I can unblock you on this. |
b183471 to
64e716b
Compare
aneta-petrova
left a comment
There was a problem hiding this comment.
I'm aware that some of the suggestions affect content you didn't author yourself but I hope that's okay because I see this as an opportunity to make sure the procedure complies with the mod docs template.
64e716b to
b878371
Compare
There was a problem hiding this comment.
According to the Modular documentation reference, custom discrete headings are not allowed in procedure modules.
For the purpose of DITA migration, we have to be strict about the structure of modules.
Let's not introduce custom headings or make this module into an actual reference module. See also Reference modules in the modularization docs.
c65f1eb to
1ab89ed
Compare
bac6e70 to
501383a
Compare
Lennonka
left a comment
There was a problem hiding this comment.
A couple of suggestions
501383a to
4ddc3b5
Compare
- Change the Insights module back to a reference module. - Restructure the content. - Remove redundant information about preinstalled package.
- Removed the custom discrete headings. - Reinstated the `Procedure` heading. - Removed the unregister step and added a link to the `Configuring Insights Client` section under Additional Resources.
23907af to
ea89c77
Compare
Lennonka
left a comment
There was a problem hiding this comment.
Nitpicks. The rest looks good!
|
@Lennonka do you think this needs a tech review, since this is just a docs change? |
|
Tech review not necessary. Thanks! |
|
Not cherry picked - there are conflicts on 3.15. cc @AkshayGadhaveRH |
Currently there are two separate insights modules under the
Performing additional configuration on Satellite Serversection:These two can be combined under a single header
Managing Insights. There are common commands listed in these two modules, and these can be listed as bullet points in a reference module rather than a procedure module.JIRA: https://issues.redhat.com/browse/SAT-28621
What changes are you introducing?
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Checklists
Please cherry-pick my commits into: