Skip to content

docs: fix V2 artifacts and content issues in routing-requests-to-rest-apis.md#5081

Open
Maanvi212006 wants to merge 1 commit into
zowe:masterfrom
Maanvi212006:fix/5077-routing-requests-v2-artifacts
Open

docs: fix V2 artifacts and content issues in routing-requests-to-rest-apis.md#5081
Maanvi212006 wants to merge 1 commit into
zowe:masterfrom
Maanvi212006:fix/5077-routing-requests-v2-artifacts

Conversation

@Maanvi212006

Copy link
Copy Markdown
Collaborator

Describe your pull request here:

Fixes V2-era artifacts and content issues in routing-requests-to-rest-apis.md so the article accurately reflects the current V3 implementation (Spring Cloud Gateway) and no longer mixes routing concepts with HA deployment architecture.

Changes:

  • Replaced "In addition to the basic Zuul routing" with "In addition to basic routing" — Zuul is V2-only and no longer part of the V3 gateway
  • Updated example URLs to use the V3 default gateway port (7554) instead of the old V2 ports (10015/10010)
  • Fixed typo: "ditributing" → "distributing"
  • Removed the empty "Implementation details for routing" heading
  • Condensed the "Zowe architecture with high availability enablement on Sysplex" section (Sysplex/LPAR/zowe.yaml/VSAM details) into a brief "High availability" summary with a link to the existing dedicated page, ../configure-sysplex.md, instead of duplicating that content here

Closes #5077

List the file(s) included in this PR:

  • docs/user-guide/api-mediation/routing-requests-to-rest-apis.md

After creating the PR, follow the instructions in the comments.

…-apis.md

Signed-off-by: Maanvi Chetwani <maanvichetwani21@gmail.com>
@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown

😺 Thank you for creating this PR!

Certain labels are needed to open a pull request in the docs-site repo, but it looks like you may not be able to add labels. That's because you either do not have permissions or you are using a fork in your PR. To publish your content to Zowe Docs, follow these steps.

  • Use comments to add labels to your pull request. Enter the /labels command in a comment to add the required review, area, and release label types.
    • Example: Enter /labels doc cli V2 to add the review: doc, area: cli, and version: V2 labels to your PR.
      • The review label indicates the kind of review your content requires. The area label indicates the content topic area. The release labels tells us the major release aligned with your content.
      • See the docs-site labels to see the labels are available for use.
    • To remove a label, use the minus sign: /labels -V2
  • Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release. Use the v3-doc-branch for Zowe V3 content.
  • Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

@zowe-robot zowe-robot added review: doc Needs review by Doc Squad member area: cli This issue is related to Zowe Command Line Interface (CLI) labels Jul 9, 2026
@zowe-robot zowe-robot added the release: V2 Zowe V2 content label Jul 9, 2026
@zowe zowe deleted a comment from Maanvi212006 Jul 9, 2026
@github-project-automation github-project-automation Bot moved this to New Issues in Zowe CLI Squad Jul 9, 2026
@Maanvi212006
Maanvi212006 requested a review from janan07 July 11, 2026 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: cli This issue is related to Zowe Command Line Interface (CLI) release: V2 Zowe V2 content review: doc Needs review by Doc Squad member

Projects

Status: New Issues

Development

Successfully merging this pull request may close these issues.

Fix V2 artifacts and content issues in routing-requests-to-rest-apis.md

2 participants