Skip to content

Conversation

@EricPonvelle
Copy link
Contributor

@EricPonvelle EricPonvelle commented Dec 18, 2025

Version(s):
enterprise-4.20+

Issue:
OSDOCS-16567

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
Updated the Web Console book for ROSA, ROSA Classic, and Dedicated to meet DITA compliance.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 18, 2025

@EricPonvelle: This pull request references OSDOCS-16567 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):
enterprise-4.20+

Issue:
OSDOCS-16567

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
Updated the Web Console book for ROSA, ROSA Classic, and Dedicated to meet DITA compliance.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 18, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Dec 18, 2025

🤖 Fri Dec 19 16:21:48 - Prow CI generated the docs preview:
https://104179--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

@EricPonvelle EricPonvelle force-pushed the OSDOCS-16567_Web-Console branch from a97cedc to 0ffe29e Compare December 18, 2025 18:11
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 18, 2025

@EricPonvelle: This pull request references OSDOCS-16567 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):
enterprise-4.20+

Issue:
OSDOCS-16567

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
Updated the Web Console book for ROSA, ROSA Classic, and Dedicated to meet DITA compliance.

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 openshift-eng/jira-lifecycle-plugin repository.

@EricPonvelle EricPonvelle force-pushed the OSDOCS-16567_Web-Console branch 3 times, most recently from cfcd79f to 3b85138 Compare December 18, 2025 19:14
[id="about-administrator-perspective_{context}"]
= Administrator role in the web console

[role="_abstract"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am under the impression that we are supposed to write "proper" short descriptions, rather than simply slap a [role="_abstract"] tag on. Is there a plan to vet these abstracts to make sure they meet the guidelines? (Not saying they don't.)
For example, in the following, the ISG says of enables: Avoid stating that inanimate objects grant abilities to people, as in “the product enables you to…”.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mburke5678 ya, we are going to do that part of the CQA process in January. This pass was to correct the broader, syntax errors that Vale flags.

Comment on lines -17 to +18
.Example
**Example**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why this change.
I don't know all the new rules. Are we not allowed to use .Example?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ya, it flags all "Block titles". This may be a changing rule, but for the sake of my task, I just rolled it to bolded.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah. Block titles can be used only in procedures? Is that right? Too many new rules!

Comment on lines +34 to +36
where:
`managementState: Removed`:: Set the `managementState` parameter value to `Removed` to disable the web console. The other valid values for this parameter are `Managed`, which enables the console under the cluster's control, and `Unmanaged`, which means that you are taking control of web console management.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add full parameter.

Suggested change
where:
`managementState: Removed`:: Set the `managementState` parameter value to `Removed` to disable the web console. The other valid values for this parameter are `Managed`, which enables the console under the cluster's control, and `Unmanaged`, which means that you are taking control of web console management.
where:
`spec.managementState.Removed`:: Set the `managementState` parameter value to `Removed` to disable the web console. The other valid values for this parameter are `Managed`, which enables the console under the cluster's control, and `Unmanaged`, which means that you are taking control of web console management.

Comment on lines +27 to +33
* xref:../operators/understanding/olm-understanding-software-catalog.adoc#olm-understanding-software-catalog[Understanding the software catalog]
* xref:../web_console/web_terminal/installing-web-terminal.adoc#installing-web-terminal[Installing the web terminal]
* link:https://docs.redhat.com/en/documentation/red_hat_openshift_lightspeed/1.0tp1/html/about/ols-about-openshift-lightspeed#ols-openshift-lightspeed-overview[{ols} overview]
* link:https://docs.redhat.com/en/documentation/red_hat_openshift_lightspeed/1.0tp1/html/install/ols-installing-lightspeed[Installing {ols}]
* link:https://docs.openshift.com/pipelines/1.14/create/working-with-pipelines-web-console.html[Working with {pipelines-title} in the web console]
* link:https://docs.openshift.com/pipelines/1.14/create/working-with-pipelines-web-console.html#op-console-statistics_working-with-pipelines-web-console[Pipeline execution statistics in the web console]
* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_serverless/1.31/html/installing_serverless/install-serverless-operator#serverless-install-web-console_install-serverless-operator[Installing the {ServerlessProductName} Operator from the web console]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we allowed only one Additional References per assembly?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a warning that flagged separated Additional Resources. This may be a malleable rule.

@EricPonvelle EricPonvelle force-pushed the OSDOCS-16567_Web-Console branch from 3b85138 to af3af32 Compare December 19, 2025 16:11
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

@openshift-ci
Copy link

openshift-ci bot commented Dec 19, 2025

@EricPonvelle: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 19, 2025

@EricPonvelle: This pull request references OSDOCS-16567 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):
enterprise-4.20+

Issue:
OSDOCS-16567

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
Updated the Web Console book for ROSA, ROSA Classic, and Dedicated to meet DITA compliance.

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 openshift-eng/jira-lifecycle-plugin repository.

@mburke5678
Copy link
Contributor

A few comments, for what they are worth. Otherwise LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.20 branch/enterprise-4.21 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants