dvcrn Gateway Validator
Safely validate gateway config changes before they break production.
How It Works
Primary approach:
- Create temp config with your changes
- Start isolated test gateway on different port
- Send test completion request
- Works? → Apply to production
- Fails? → Block and show error
Fallback approach (when isolated gateway can't start):
- Validate config syntax
- Test provider APIs directly (check API keys, models)
- Works? → Apply to production
- Fails? → Block and show error
Usage
I'll automatically use this when you request gateway changes:
- "Change model to gpt-4o"
- "Update API key"
- "Switch to anthropic"
- Any config modification
Examples
Bad API Key
You: "Set API key to fake-key"
Me: "🧪 Testing changes...
❌ API key is invalid
Config unchanged."
Bad Model
You: "Use model gpt-99"
Me: "🧪 Testing changes...
❌ Model not found
Config unchanged."
Valid Change
You: "Change temperature to 0.5"
Me: "🧪 Testing changes...
✅ Test passed
✅ Config updated"
Technical Details
Level 1: Config Syntax
- YAML valid?
- Required fields present?
- Value ranges valid (temp 0-2, etc.)?
Level 2: Provider Test (direct API calls)
- API key valid?
- Model exists?
- Can connect to provider?
Level 3: Full Gateway Test (when possible)
- Start temp gateway
- Send completion request
- Verify end-to-end works
Limitations
- Isolated gateway test requires systemd/launchd (not available in all containers)
- When isolated test unavailable, falls back to provider-level validation
- Provider testing needs ~5-10 seconds for API calls