Skip to content

ROSAENG-00000 | docs: expand CLI abbreviations for product documentation compliance (OSDOCS-16406) - #3345

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
EricPonvelle:OSDOCS-16406_rosa-updates
Jul 14, 2026
Merged

ROSAENG-00000 | docs: expand CLI abbreviations for product documentation compliance (OSDOCS-16406)#3345
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
EricPonvelle:OSDOCS-16406_rosa-updates

Conversation

@EricPonvelle

@EricPonvelle EricPonvelle commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

This PR addresses:

Detailed Description of the Issue

This PR addresses some language issues that were not in compliance with product documentation standards. Since we generate our CLI documentation from this repo, the updates had to be done here. To that end, I have changed the descriptions on a few ROSA commands so that they have the full names rather than acronyms.

Type of Change

  • feat - adds a new user-facing capability.
  • fix - resolves an incorrect behavior or bug.
  • docs - updates documentation only.
  • style - formatting or naming changes with no logic impact.
  • refactor - code restructuring with no behavior change.
  • test - adds or updates tests only.
  • chore - maintenance work (tooling, housekeeping, non-product code).
  • build - changes build system, packaging, or dependencies for build output.
  • ci - changes CI pipelines, jobs, or automation workflows.
  • perf - improves performance without changing intended behavior.

Developer Verification Checklist

  • Commit subject/title follows [JIRA-TICKET] | [TYPE]: <MESSAGE>.
  • PR description clearly explains both what changed and why.
  • Relevant Jira/GitHub issues and related PRs are linked.
  • make install-hooks has been run in this clone.
  • Tests were added/updated where appropriate.
  • I manually tested the change.
  • make test passes.
  • make lint passes.
  • make rosa passes.
  • Documentation or repo-local agent guidance was added/updated where appropriate.
  • Any risk, limitation, or follow-up work is documented.

Summary by CodeRabbit

  • Documentation
    • Improved CLI help text across multiple commands (create, delete, list, link, unlink, and verify) with clearer, standardized capitalization and phrasing.
    • Expanded common abbreviations (DNS, IDP, OIDC, IAM) into full terms for more consistent user-facing wording.
    • Updated help content to reference “Red Hat Hybrid Cloud Console” where applicable and to more precisely describe cluster context (including VPC subnets and non-AWS STS wording).

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 7, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 7, 2026

Copy link
Copy Markdown

@EricPonvelle: This pull request references OSDOCS-16406 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

This PR addresses:

Detailed Description of the Issue

This PR addresses some language issues that were not in compliance with product documentation standards. Since we generate our CLI documentation from this repo, the updates had to be done here. To that end, I have changed the descriptions on a few ROSA commands so that they have the full names rather than acronyms.

Type of Change

  • feat - adds a new user-facing capability.
  • fix - resolves an incorrect behavior or bug.
  • docs - updates documentation only.
  • style - formatting or naming changes with no logic impact.
  • refactor - code restructuring with no behavior change.
  • test - adds or updates tests only.
  • chore - maintenance work (tooling, housekeeping, non-product code).
  • build - changes build system, packaging, or dependencies for build output.
  • ci - changes CI pipelines, jobs, or automation workflows.
  • perf - improves performance without changing intended behavior.

Developer Verification Checklist

  • Commit subject/title follows [JIRA-TICKET] | [TYPE]: <MESSAGE>.
  • PR description clearly explains both what changed and why.
  • Relevant Jira/GitHub issues and related PRs are linked.
  • make install-hooks has been run in this clone.
  • Tests were added/updated where appropriate.
  • I manually tested the change.
  • make test passes.
  • make lint passes.
  • make rosa passes.
  • Documentation or repo-local agent guidance was added/updated where appropriate.
  • Any risk, limitation, or follow-up work is documented.

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.

@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

This pull request updates Cobra command help text across create, delete, unlink, list, link, and verify commands. Several create commands now spell out DNS, OIDC, IAM, and identity provider terms, and ocm-role now refers to Red Hat Hybrid Cloud Console and adds a permissions boundary example. Delete, unlink, and list commands adjust wording and capitalization, and verify commands expand VPC and STS phrasing. No command flags or runtime behavior changed.

🚥 Pre-merge checks | ✅ 13 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check ⚠️ Warning The description includes issues and a detailed issue note, but omits most required template sections like summary, testing, and behavior changes. Add the missing template sections: PR Summary, Related Issues and PRs details, Previous/After Behavior, How to Test, Proof of Fix, Breaking Changes, and verification items.
✅ Passed checks (13 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed Diff only touches Cobra command help strings in cmd/*.go; no _test.go files or Ginkgo titles were changed.
Test Structure And Quality ✅ Passed PR only changes Cobra help text files; no Ginkgo test files or test logic were added or modified.
Microshift Test Compatibility ✅ Passed The PR only changes cobra command help text in cmd/*.go; no Ginkgo e2e tests or MicroShift-sensitive APIs were added.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PASS: The PR adds only CLI help-text updates and unit Ginkgo specs; no e2e tests or multi-node/HA assumptions, and no SNO-specific topology checks were needed.
Topology-Aware Scheduling Compatibility ✅ Passed PASS: HEAD only updates Cobra help strings in cmd/*; no manifests, controllers, affinity, node selectors, or topology-aware scheduling logic changed.
Ote Binary Stdout Contract ✅ Passed Diff only updates Cobra help strings; no main/init/TestMain/suite-setup stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR only changes Cobra help strings in cmd/*; diff contains no new Ginkgo tests, IPv4 literals, or external-network calls.
No-Weak-Crypto ✅ Passed Touched files only change Cobra help text; scans found no weak crypto or secret-comparison code in the PR.
Container-Privileges ✅ Passed PR only edits Cobra help strings in cmd/*.go; no container/K8s manifests or privileged settings appear in the diff.
No-Sensitive-Data-In-Logs ✅ Passed The diff only updates Cobra help strings/examples; no new logging calls or sensitive data were introduced.
Title check ✅ Passed The title clearly summarizes the main change: expanding CLI abbreviations for documentation compliance.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@cmd/create/idp/cmd.go`:
- Around line 92-93: Tighten the help text in the command definition by updating
the `Short` and `Long` descriptions to use clearer wording: change the phrase in
the `cmd/create/idp/cmd.go` command metadata so it reads naturally as “Add
identity provider (IDP) for a cluster” and rephrase the longer description to
avoid “identity providers” in the awkward plural form. Keep the fix confined to
the `Short` and `Long` fields in the `createIDPCmd` command setup.

In `@cmd/create/oidcconfig/cmd.go`:
- Around line 57-58: Update the user-facing long description in the OIDC config
command metadata so the help text uses “an S3 bucket” instead of “a S3 bucket.”
Make this change in the command definition where the OpenID Connect config
description is built, keeping the rest of the wording unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 92ddc5da-4fd9-4965-a78c-1522ad0a5e4d

📥 Commits

Reviewing files that changed from the base of the PR and between f9db553 and db3f59a.

📒 Files selected for processing (5)
  • cmd/create/dnsdomains/cmd.go
  • cmd/create/idp/cmd.go
  • cmd/create/ocmrole/cmd.go
  • cmd/create/oidcconfig/cmd.go
  • cmd/create/oidcprovider/cmd.go

Comment thread cmd/create/idp/cmd.go Outdated
Comment thread cmd/create/oidcconfig/cmd.go Outdated
@EricPonvelle
EricPonvelle force-pushed the OSDOCS-16406_rosa-updates branch from db3f59a to 0efd712 Compare July 8, 2026 14:09

@bhardesty bhardesty left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Just noticed one small spacing issue.

Comment thread cmd/create/operatorroles/cmd.go Outdated
@EricPonvelle
EricPonvelle force-pushed the OSDOCS-16406_rosa-updates branch 2 times, most recently from ab7f08f to 68ad034 Compare July 8, 2026 22:34
Comment thread cmd/dlt/idp/cmd.go Outdated
Comment thread cmd/list/idp/cmd.go Outdated
Comment thread cmd/dlt/ocmrole/cmd.go Outdated
Comment thread cmd/create/oidcprovider/cmd.go Outdated
Comment thread cmd/list/ingress/cmd.go Outdated
Comment thread cmd/dlt/ocmrole/cmd.go Outdated
@olucasfreitas

Copy link
Copy Markdown
Contributor

@EricPonvelle The commit message format needs to match the repo convention: OSDOCS-16406 | docs: <description>. This is likely why ci/prow/commits is failing.

@EricPonvelle EricPonvelle changed the title OSDOCS-16406: Suggested CLI changes to comply with product documentation OSDOCS-16406 | docs: Suggested CLI changes to comply with product documentation Jul 10, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 10, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@EricPonvelle: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

This PR addresses:

Detailed Description of the Issue

This PR addresses some language issues that were not in compliance with product documentation standards. Since we generate our CLI documentation from this repo, the updates had to be done here. To that end, I have changed the descriptions on a few ROSA commands so that they have the full names rather than acronyms.

Type of Change

  • feat - adds a new user-facing capability.
  • fix - resolves an incorrect behavior or bug.
  • docs - updates documentation only.
  • style - formatting or naming changes with no logic impact.
  • refactor - code restructuring with no behavior change.
  • test - adds or updates tests only.
  • chore - maintenance work (tooling, housekeeping, non-product code).
  • build - changes build system, packaging, or dependencies for build output.
  • ci - changes CI pipelines, jobs, or automation workflows.
  • perf - improves performance without changing intended behavior.

Developer Verification Checklist

  • Commit subject/title follows [JIRA-TICKET] | [TYPE]: <MESSAGE>.
  • PR description clearly explains both what changed and why.
  • Relevant Jira/GitHub issues and related PRs are linked.
  • make install-hooks has been run in this clone.
  • Tests were added/updated where appropriate.
  • I manually tested the change.
  • make test passes.
  • make lint passes.
  • make rosa passes.
  • Documentation or repo-local agent guidance was added/updated where appropriate.
  • Any risk, limitation, or follow-up work is documented.

Summary by CodeRabbit

  • Documentation
  • Improved CLI help text across multiple commands (create, delete, list, link, unlink, and verify) with clearer descriptions and standardized capitalization.
  • Expanded common abbreviations (DNS, IDP, OIDC, IAM) into full terms in user-facing wording.
  • Updated help content to better reference “Red Hat Hybrid Cloud Console” and more precisely describe identity and access management and cluster context.

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-16406_rosa-updates branch from 68ad034 to d3d708f Compare July 10, 2026 22:10
@EricPonvelle

Copy link
Copy Markdown
Contributor Author

@olucasfreitas Thanks for that review! I think I addressed everything correctly that you pointed out, and I updated the commit message. Let me know if you spot anything else I need to fix.

@EricPonvelle EricPonvelle changed the title OSDOCS-16406 | docs: Suggested CLI changes to comply with product documentation ROSAENG-00000 | docs: expand CLI abbreviations for product documentation compliance (OSDOCS-16406) Jul 13, 2026
@EricPonvelle
EricPonvelle force-pushed the OSDOCS-16406_rosa-updates branch 2 times, most recently from f104178 to 78b7e2f Compare July 13, 2026 19:57
@EricPonvelle
EricPonvelle force-pushed the OSDOCS-16406_rosa-updates branch from 78b7e2f to ca87448 Compare July 13, 2026 20:58
@openshift-ci

openshift-ci Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

@EricPonvelle: EricPonvelle unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

Details

In response to this:

/override ci/prow/lint /override ci/prow/govulncheck /override ci/prow/security

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.

@EricPonvelle

Copy link
Copy Markdown
Contributor Author

/override ci/prow/lint
/override ci/prow/govulncheck
/override ci/prow/security

@openshift-ci

openshift-ci Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

@EricPonvelle: EricPonvelle unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

Details

In response to this:

/override ci/prow/lint
/override ci/prow/govulncheck
/override ci/prow/security

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.

@olucasfreitas

Copy link
Copy Markdown
Contributor

/override ci/prow/lint
/override ci/prow/govulncheck
/override ci/prow/security

@openshift-ci

openshift-ci Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

@olucasfreitas: Overrode contexts on behalf of olucasfreitas: ci/prow/govulncheck, ci/prow/lint, ci/prow/security

Details

In response to this:

/override ci/prow/lint
/override ci/prow/govulncheck
/override ci/prow/security

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.

@olucasfreitas

olucasfreitas commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

@EricPonvelle Just needs a make fmt run to fix gci formatting on the 4 concatenated files, then I'll /override ci/prow/lint for the pre-existing staticcheck issues. The govulncheck and security failures are also unrelated — /override ci/prow/govulncheck and /override ci/prow/security.

@olucasfreitas

Copy link
Copy Markdown
Contributor

/override ci/prow/lint
/override ci/prow/govulncheck
/override ci/prow/security
/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 14, 2026
@openshift-ci

openshift-ci Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: EricPonvelle, olucasfreitas

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 14, 2026
@openshift-ci

openshift-ci Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

@olucasfreitas: Overrode contexts on behalf of olucasfreitas: ci/prow/govulncheck, ci/prow/lint, ci/prow/security

Details

In response to this:

/override ci/prow/lint
/override ci/prow/govulncheck
/override ci/prow/security
/lgtm
/approve

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.

@openshift-ci

openshift-ci Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

@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-merge-bot
openshift-merge-bot Bot merged commit e4eecdd into openshift:master Jul 14, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants