-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS-3390: ROSA documentation restructure updates #43807
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
Conversation
✅ Deploy Preview for osdocs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
ef3db56 to
f9b81ac
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.
This file fell out of sync in the first phase of the restructure. It was my fault. Are the links still correct?
a6713ce to
6d2e942
Compare
4440da4 to
c57aa49
Compare
_topic_maps/_topic_map_rosa.yml
Outdated
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 commented out Accessing a ROSA cluster and Configuring identity providers using the Red Hat OpenShift Cluster Manager because they are duplicates of the assemblies in the Installing, accessing, and deleting ROSA clusters directory. If everyone is okay with me removing those files, I will do so.
_topic_maps/_topic_map_rosa.yml
Outdated
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.
Does the Command quick reference for creating clusters and users apply to STS as well? If so, should it be moved up a directory level?
c57aa49 to
1ab3686
Compare
1ab3686 to
4398f34
Compare
|
@bmcelvee hi! This restructuring looks really great! I have one small suggestion, but I can't access the relevant area of the topic map for comment in the Files changed tab. So, I'll add it here. In the topic map, you could move "Upgrading ROSA with STS" to be before "Upgrading ROSA", given that STS deployments have primary focus elsewhere in the library. For example: |
4398f34 to
670e0e7
Compare
|
Acks required Preview: https://deploy-preview-43807--osdocs.netlify.app/openshift-rosa/latest/welcome/index.html Hi! Would you all mind giving this restructure update a review and ack, please? Thanks! |
|
This looks great! |
670e0e7 to
84daf50
Compare
|
lgtm |
|
/cherrypick enterprise-4.10 |
|
/cherrypick enterprise-4.11 |
|
@bmcelvee: new pull request created: #44581 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@bmcelvee: new pull request created: #44582 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
https://issues.redhat.com/browse/OSDOCS-3390
Original restructure PR for reference: #41923
Acks required
QE: @yuwang-RH
Eng/PM: @okashi18, @arendej
Product Experience: @davemulford
Docs: @AndrewJones-RH
Preview: https://deploy-preview-43807--osdocs.netlify.app/openshift-rosa/latest/welcome/index.html
Would you all mind giving the new ROSA docs structure a review and ack, please?