Skip to content

[docs-agent] Update API documentation — rename Regional Platform to HyperFleet in docs/titles - #118

Closed
redhat-chai-bot wants to merge 1 commit into
openshift-online:mainfrom
redhat-chai-bot:docs/update-api-2026-07-03
Closed

[docs-agent] Update API documentation — rename Regional Platform to HyperFleet in docs/titles#118
redhat-chai-bot wants to merge 1 commit into
openshift-online:mainfrom
redhat-chai-bot:docs/update-api-2026-07-03

Conversation

@redhat-chai-bot

@redhat-chai-bot redhat-chai-bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Automated Documentation Update

Changes Made

Renamed "ROSA Regional Platform" to "ROSA HyperFleet" in documentation prose and titles across 7 files:

  • CLAUDE.md — project description updated
  • AGENTS.md — agent description updated
  • README.md — title, Swagger URL path, prose references, ci-operator config path
  • openapi/openapi.yaml — API title in OpenAPI spec
  • SECURITY-AUDIT.md — document title
  • test/e2e-api/README.md — prose description
  • docs/api/zoa-endpoints.md — 3 cross-repo links updated from rosa-regional-platform to rosa-hyperfleet

Triggered By

Recent PRs (last 7 days):

Platform repo #665 renamed all references from "ROSA Regional Platform" to "ROSA HyperFleet", but this API repo still had 40+ stale references.

Overall Documentation Validation:

  • 14 prose/title references to old project name fixed
  • Formatting standardized with prettier

Deliberately left unfixed:

  • go.mod module path (github.com/openshift/rosa-regional-platform-api) — changing would break all imports
  • CLAUDE.md/AGENTS.md references to the go.mod module path — accurately reflect the real value
  • deployment/ manifests, Helm charts, ArgoCD apps — live k8s resource/namespace names
  • quay.io container image references in README.md — may be actual image names
  • k8s service hostnames in SECURITY-AUDIT.md — reflect actual deployed names

/cc @jmelis @slopezz @iamkirkbater @ravitri — please review these updates.


Generated by Chai Bot documentation update task (weekly validation).

Summary by CodeRabbit

  • Documentation
    • Renamed the API branding across docs and the OpenAPI spec to ROSA HyperFleet API.
    • Reworked endpoint and setup documentation for clearer tables, examples, and troubleshooting guidance.
    • Expanded E2E testing instructions with more detailed run options, environment setup, and container usage examples.
    • Updated related links and references to match the new project name.

@openshift-ci

openshift-ci Bot commented Jul 3, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: redhat-chai-bot
Once this PR has been reviewed and has the lgtm label, please assign slopezz for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jul 3, 2026
@openshift-ci

openshift-ci Bot commented Jul 3, 2026

Copy link
Copy Markdown

Hi @redhat-chai-bot. Thanks for your PR.

I'm waiting for a openshift-online member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

This PR renames the project from "ROSA Regional Platform API" to "ROSA HyperFleet API" across AGENTS.md, CLAUDE.md, README.md, SECURITY-AUDIT.md, openapi.yaml, and test/e2e-api/README.md. It also reformats documentation content into markdown tables, expands README E2E testing/troubleshooting instructions, and updates SECURITY-AUDIT.md findings narrative.

Changes

Rebrand and documentation updates

Layer / File(s) Summary
API name rebrand across docs and spec
AGENTS.md, CLAUDE.md, README.md, openapi/openapi.yaml, test/e2e-api/README.md, SECURITY-AUDIT.md
Renames the API from "ROSA Regional Platform API" to "ROSA HyperFleet API" and adds minor blank-line formatting fixes.
README configuration and testing docs
README.md
Reformats the flags table and expands local/unit test instructions with package-scoped, authz-only, and coverage variants.
README containerized E2E test instructions
README.md
Rewrites container E2E commands with FOCUS/SKIP/AWS_CREDENTIALS_PATH support, ~/.aws mounting, Podman alternative, and multi-arch build guidance.
README AWS credentials troubleshooting
README.md
Expands credentials check expectations, common issues, a static-credentials workaround, and interactive debugging steps.
README authorization E2E and API examples
README.md
Switches authorization E2E infra/Prow CI references to HyperFleet context and updates awscurl API examples.
SECURITY-AUDIT.md findings content updates
SECURITY-AUDIT.md
Expands Attack Vectors/What to Mitigate content and adjusts the cfg.Authz code snippet and Risk paragraph in Finding 3.
zoa-endpoints.md table reformatting
docs/api/zoa-endpoints.md
Reformats endpoint documentation sections into markdown tables and updates related documentation links to rosa-hyperfleet.

Estimated code review effort: 2 (Simple) | ~12 minutes

Suggested labels: do-not-merge/hold

🚥 Pre-merge checks | ✅ 10 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Ai-Attribution ⚠️ Warning PR text says it was generated by Chai Bot, but the tip commit has no Assisted-by/Generated-by trailer—only the subject line. Add a Red Hat attribution trailer (e.g. Generated-by: or Assisted-by:) to the PR commit message; do not use Co-Authored-By for AI tools.
✅ Passed checks (10 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: a documentation rename from Regional Platform to HyperFleet across docs titles.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
No-Weak-Crypto ✅ Passed Patch only renames docs/titles; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or non-constant-time secret compares were added.
Container-Privileges ✅ Passed Docs-only PR; no container/K8s manifests changed and no privileged/host* or allowPrivilegeEscalation settings found in the diff.
No-Sensitive-Data-In-Logs ✅ Passed PR only updates documentation; no new logging code or real secrets/PII were introduced. Token/session examples are placeholders.
No-Hardcoded-Secrets ✅ Passed Patch only renames docs/titles in Markdown/YAML; no API keys, tokens, passwords, private keys, embedded credentials, or long base64 literals were added.
No-Injection-Vectors ✅ Passed PR only updates docs/metadata; no SQL concat, eval/exec, pickle.loads, yaml.load, os.system, or dangerouslySetInnerHTML changes were added.
✨ 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
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🤖 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 `@openapi/openapi.yaml`:
- Line 3: The Swagger UI title is still hardcoded with the old spec name, so
update the title used by the swagger generation path to match the renamed API.
In particular, adjust the `make generate-swagger` template in `Makefile` so the
generated UI title stays aligned with `ROSA HyperFleet API`, and verify any
other swagger title string constants used by the generation flow are updated
consistently.

In `@README.md`:
- Around line 215-221: The custom credentials path example in the README uses
the wrong shell syntax, so update the `make test-e2e-container` example to use
the `PWD` environment variable form instead of command substitution. Fix the
snippet under the “Using credentials from a custom location” section so
`AWS_CREDENTIALS_PATH` references the current directory via `$PWD` or `${PWD}`.

In `@test/e2e-api/README.md`:
- Line 3: The README rename is inconsistent with the suite banner, because
test/e2e-api/e2e_test.go still prints the old “ROSA Regional Platform API E2E
Suite” text. Update the banner string in the e2e test entrypoint (the code that
prints the suite name, likely in e2e_test.go/main test setup) so it matches the
README’s “ROSA HyperFleet API” terminology and both docs and runtime output use
the same name.
🪄 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: openshift-online/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: cf266577-79f6-4fe4-b3c5-1ce53bf4307a

📥 Commits

Reviewing files that changed from the base of the PR and between 4521cd6 and 13a3239.

📒 Files selected for processing (7)
  • AGENTS.md
  • CLAUDE.md
  • README.md
  • SECURITY-AUDIT.md
  • docs/api/zoa-endpoints.md
  • openapi/openapi.yaml
  • test/e2e-api/README.md

Comment thread openapi/openapi.yaml
openapi: 3.0.3
info:
title: ROSA Regional Platform API
title: ROSA HyperFleet API

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.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Keep the Swagger UI title in sync with the spec rename.

make generate-swagger still hardcodes ROSA Regional Platform API - Swagger UI in Makefile, so regenerating docs will leave the checked-in Swagger page with the old name unless that template is updated too.

🤖 Prompt for 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.

In `@openapi/openapi.yaml` at line 3, The Swagger UI title is still hardcoded with
the old spec name, so update the title used by the swagger generation path to
match the renamed API. In particular, adjust the `make generate-swagger`
template in `Makefile` so the generated UI title stays aligned with `ROSA
HyperFleet API`, and verify any other swagger title string constants used by the
generation flow are updated consistently.

Comment thread README.md
Comment on lines 215 to 221
**Using credentials from a custom location**:

```bash
make test-e2e-container \
BASE_URL="https://xxxxx.execute-api.us-east-2.amazonaws.com/prod" \
AWS_CREDENTIALS_PATH="$(PWD)/../my-credentials-dir"
```

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.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Fix the custom credentials path example.

$(PWD) is command substitution, not the current-directory variable, so this example will fail. Use $PWD (or ${PWD}) instead.

Patch
-  AWS_CREDENTIALS_PATH="$(PWD)/../my-credentials-dir"
+  AWS_CREDENTIALS_PATH="$PWD/../my-credentials-dir"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
**Using credentials from a custom location**:
```bash
make test-e2e-container \
BASE_URL="https://xxxxx.execute-api.us-east-2.amazonaws.com/prod" \
AWS_CREDENTIALS_PATH="$(PWD)/../my-credentials-dir"
```
**Using credentials from a custom location**:
🤖 Prompt for 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.

In `@README.md` around lines 215 - 221, The custom credentials path example in the
README uses the wrong shell syntax, so update the `make test-e2e-container`
example to use the `PWD` environment variable form instead of command
substitution. Fix the snippet under the “Using credentials from a custom
location” section so `AWS_CREDENTIALS_PATH` references the current directory via
`$PWD` or `${PWD}`.

Comment thread test/e2e-api/README.md
# E2E Tests

End-to-end integration and functional tests for the ROSA Regional Platform API.
End-to-end integration and functional tests for the ROSA HyperFleet API.

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.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Align the README with the suite banner.

test/e2e-api/e2e_test.go still prints ROSA Regional Platform API E2E Suite, so the docs rename and the runtime output will diverge until that string is updated too.

🤖 Prompt for 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.

In `@test/e2e-api/README.md` at line 3, The README rename is inconsistent with the
suite banner, because test/e2e-api/e2e_test.go still prints the old “ROSA
Regional Platform API E2E Suite” text. Update the banner string in the e2e test
entrypoint (the code that prints the suite name, likely in e2e_test.go/main test
setup) so it matches the README’s “ROSA HyperFleet API” terminology and both
docs and runtime output use the same name.

@redhat-chai-bot

Copy link
Copy Markdown
Contributor Author

Auto-closing: this documentation update was not reviewed within 3 days. If the changes are still relevant, a new PR will be opened in a future run.

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

Labels

needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant