-
Notifications
You must be signed in to change notification settings - Fork 133
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
Add section for enabling/disabling components by groups #3962
Conversation
Add info on how to enable or disable certain component groups Signed-off-by: 1000TurquoisePogs <[email protected]>
Signed-off-by: 1000TurquoisePogs <[email protected]>
😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
📁 The PR description is missing the file name(s) for the updated content. List all the files included in this PR so this information displays in our Zowe Docs GitHub Slack channel. If you have addressed this issue already, refresh this page in your browser to remove this comment. |
Do NOT merge this yet - I am discussing how best to clean references to the page that this PR replaces. |
Signed-off-by: 1000TurquoisePogs <[email protected]>
Signed-off-by: Andrew Jandacek <[email protected]>
Signed-off-by: 1000TurquoisePogs <[email protected]>
This PR resolves #3932 by taking the table within that PR and inserting it in the page about how to manage components and extensions.
That page already had a topic on enabling and disabling components, so it was a small addition to just add a table suggesting which components are related and what they do.
With this, I was able to remove the older APIML-specific page, simplifying the doc slightly.