Skip to content

Conversation

@srini-abhiram
Copy link
Contributor

@srini-abhiram srini-abhiram commented Dec 1, 2025

Close #234

  • Make sure the code changes pass the pre-commit checks.
  • Sign-off your commit by using -s when doing git commit
  • Try to classify PRs for easy understanding of the type of changes, such as [Bugfix], [Feat], and [CI].
Detailed Checklist (Click to Expand)

Thank you for your contribution to semantic-router! Before submitting the pull request, please ensure the PR meets the following criteria. This helps us maintain the code quality and improve the efficiency of the review process.

PR Title and Classification

Please try to classify PRs for easy understanding of the type of changes. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

  • [Bugfix] for bug fixes.
  • [CI/Build] for build or continuous integration improvements.
  • [Doc] for documentation fixes and improvements.
  • [Feat] for new features in the cluster (e.g., autoscaling, disaggregated prefill, etc.).
  • [Router] for changes to the vllm_router (e.g., routing algorithm, router observability, etc.).
  • [Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.

Code Quality

The PR need to meet the following code quality standards:

  • Pass all linter checks. Please use pre-commit to format your code. See README.md for installation.
  • The code need to be well-documented to ensure future contributors can easily understand the code.
  • Please include sufficient tests to ensure the change is stay correct and robust. This includes both unit tests and integration tests.

DCO and Signed-off-by

When contributing changes to this project, you must agree to the DCO. Commits must include a Signed-off-by: header which certifies agreement with the terms of the DCO.

Using -s with git commit will automatically add this header.

What to Expect for the Reviews

Implements the initial version of the VSR CLI with the following commands: config, deploy, get, install, logs, status, test-prompt.

- Added Cobra-based CLI structure

- Implemented configuration management

- Added deployment support for Local, Docker, and Kubernetes

- Added documentation in website/docs/cli
@netlify
Copy link

netlify bot commented Dec 1, 2025

Deploy Preview for vllm-semantic-router ready!

Name Link
🔨 Latest commit d8ae372
🔍 Latest deploy log https://app.netlify.com/projects/vllm-semantic-router/deploys/692ea0bc6368780008b89535
😎 Deploy Preview https://deploy-preview-750--vllm-semantic-router.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@Xunzhuo
Copy link
Member

Xunzhuo commented Dec 1, 2025

can you share screenshot?

yossiovadia and others added 6 commits December 2, 2025 08:17
templating logic of the OPENAI_API_KEY

Signed-off-by: Sanjeev Rampal <[email protected]>
…ssue vllm-project#234)

Completes the VSR CLI tool implementation with all remaining commands, comprehensive test coverage, and full documentation.

- Added model management commands (list, info, validate, remove, download)
- Added debug and diagnostics commands (debug, health, diagnose)
- Added monitoring commands (dashboard, metrics)
- Added utility commands (completion, upgrade, undeploy)
- Implemented Helm deployment support (4th deployment environment)
- Added comprehensive test coverage (15 test files, 109 test functions, 93+ test cases)
- Created detailed documentation (README, quick start guide, test coverage report)
- Enhanced deployment lifecycle with graceful shutdown and health checks
- Implemented multi-environment auto-detection for status and logs
- Added shell completion support for bash, zsh, fish, and powershell

Signed-off-by: Srinivas A <[email protected]>
Updates the main README with detailed VSR CLI usage instructions,
replacing the previous brief CLI section with comprehensive guidance.

- Added installation instructions with verification step
- Added quick start guide (4 commands to deploy)
- Listed key features (multi-environment, model management, monitoring)
- Provided common command examples with descriptions
- Added links to detailed CLI documentation and quick start guide

This provides users with a clear entry point to the VSR CLI tool
and highlights its capabilities for simplified deployment and management.

Signed-off-by: Srinivas A <[email protected]>
This commit addresses 6 critical issues identified during code review,
plus build improvements for better user experience.

Critical fixes:
- Issue vllm-project#1: PID file race condition - kill router process if PID file
  write fails to prevent untrackable processes
- Issue vllm-project#2: Cross-platform compatibility - replace hardcoded /tmp paths
  with os.TempDir() and add user-specific suffixes using os.Getuid()
- Issue vllm-project#3: Signal handling - add graceful shutdown for port-forward
  process on Ctrl+C to prevent orphaned kubectl processes
- Issue vllm-project#4: HTTP timeout - add 30-second timeout to prevent hanging
  requests in test command
- Issue vllm-project#5: Security - restrict log/PID file permissions to 0600
- Issue vllm-project#6: Input validation - enforce 10k character limit on prompts

Build improvements:
- Embed library path using -ldflags="-r" to eliminate need for users
  to manually set LD_LIBRARY_PATH when running vsr binary

Files modified:
- src/semantic-router/pkg/cli/deployment/deployment.go
- src/semantic-router/pkg/cli/deployment/upgrade.go
- src/semantic-router/cmd/vsr/commands/dashboard.go
- src/semantic-router/cmd/vsr/commands/test.go
- tools/make/build-run-test.mk
- src/semantic-router/pkg/cli/deployment/deployment_test.go

All fixes have been verified with standalone test programs.

Signed-off-by: Srinivas A <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add VSR CLI Support for Enhanced User Experience

4 participants