Skip to content

fix: update API server paths in README to point to legacy directory - #226

Open
pratik-naik003 wants to merge 1 commit into
kubeflow:mainfrom
pratik-naik003:fix/issue-225-api-paths
Open

fix: update API server paths in README to point to legacy directory#226
pratik-naik003 wants to merge 1 commit into
kubeflow:mainfrom
pratik-naik003:fix/issue-225-api-paths

Conversation

@pratik-naik003

Copy link
Copy Markdown

Fixes #225

The server/ and server-https/ directories have been moved inside the legacy/ folder, but the Usage section in the README.md file still points to the old root paths. This PR updates the startup commands in the README to reflect the correct directory structure by prepending legacy/ to the paths, preventing FileNotFoundError for new users.

[x] My commits are signed off (git commit -s)

Testing

  • Unit tests
  • Integration tests
  • E2E tests
  • Manually tested (describe below)

Manually verified that the legacy/server and legacy/server-https directories exist and the updated paths in the README are now accurate.

Signed-off-by: pratik naik <naikp0241@gmail.com>
@google-oss-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tarekabouzeid for approval. For more information see the Kubernetes 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

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: update API server paths in README to point to legacy directory

1 participant