Skip to content

feat: Add LiteLLM Testbed#7

Open
marcelfzr wants to merge 4 commits into
mainfrom
feat/litellm-testbed
Open

feat: Add LiteLLM Testbed#7
marcelfzr wants to merge 4 commits into
mainfrom
feat/litellm-testbed

Conversation

@marcelfzr
Copy link
Copy Markdown
Member

Description

Add a reproducible LiteLLM Proxy testbed for Naira plugin development and integration testing.

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to change)
  • 📝 Documentation update
  • 🔧 Refactoring (no functional changes)
  • 🏗️ Infrastructure / CI / Helm

How Has This Been Tested?

  • go test ./... passes
  • helm lint passes
  • Manual testing via Docker Compose
  • Manual testing on Kubernetes

Checklist

  • My code follows the project's coding standards (AGENTS.md)
  • I have added tests that prove my fix/feature works
  • New and existing unit tests pass locally
  • I have updated the documentation (if applicable)
  • My changes generate no new warnings

@marcelfzr marcelfzr requested a review from a team June 1, 2026 09:30
@marcelfzr marcelfzr requested review from a team as code owners June 1, 2026 09:30
Copy link
Copy Markdown

@hosseinsalahi hosseinsalahi left a comment

Choose a reason for hiding this comment

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

the rest looks good to me.

Comment thread Makefile
## Check LiteLLM manifests for plaintext API key values.
testbed-litellm-secret-scan:
@echo ">>> Checking $(LITELLM_DIR) for plaintext LiteLLM API keys..."
@awk '/api_key:/ && $$0 !~ /os.environ\/MISTRAL_API_KEY/ { print FILENAME ":" FNR ":" $$0; found=1 } END { exit found }' $(LITELLM_DIR)/*.yaml
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

secret-scan awk pattern is narrow. It only flags lines containing api_key: not matching os.environ/MISTRAL_API_KEY. A future second provider (e.g. os.environ/OPENAI_API_KEY) would be flagged as a plaintext leak. Consider matching os.environ/ more generally:

$0 !~ /api_key: os.environ\//

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.

2 participants