[MIGRATION] Issues from legacy repo (cliproxyapi)

[KooshaPari]

Migration Notes

These issues were created in the legacy repo (cliproxyapi) and need to be reviewed/migrated to this repo.

Legacy Repo: https://github.com/KooshaPari/cliproxyapi

Issues to Migrate (30 total, created 2026-02-21 to 2026-02-24):

High Priority

• [CodeScanning #48] go/clear-text-logging in pkg/llmproxy/thinking/apply.go:280 #115 Implement TLS/mTLS Support (security)
• [CodeScanning #52] go/clear-text-logging in pkg/llmproxy/thinking/validate.go:272 #105 Create Provider Configuration Guide
• [CodeScanning #54] go/clear-text-logging in pkg/llmproxy/watcher/clients.go:60 #104 Create API Reference Documentation
• [CodeScanning #55] go/clear-text-logging in pkg/llmproxy/watcher/clients.go:115 #103 Handle Provider Service Outages
• [CodeScanning #53] go/clear-text-logging in pkg/llmproxy/thinking/validate.go:370 #102 Handle Token Expiry During Request
• [CodeScanning #56] go/clear-text-logging in pkg/llmproxy/watcher/clients.go:116 #101 Handle Provider Rate Limit Cascading
• [CodeScanning #55] go/clear-text-logging in pkg/llmproxy/watcher/clients.go:115 #98 Create Recovery Runbook
• [CodeScanning #57] go/clear-text-logging in pkg/llmproxy/watcher/clients.go:117 #99 Implement Tenant Identification

Medium Priority

• [CodeScanning #44] go/clear-text-logging in pkg/llmproxy/thinking/apply.go:191 #122 Implement Provider Cost Tracking
• [CodeScanning #46] go/clear-text-logging in pkg/llmproxy/thinking/apply.go:264 #119 Implement Provider Health Dashboard
• [CodeScanning #47] go/clear-text-logging in pkg/llmproxy/thinking/apply.go:273 #117 Implement Request ID Tracking
• [CodeScanning #47] go/clear-text-logging in pkg/llmproxy/thinking/apply.go:273 #116 Implement CORS Configuration
• [CodeScanning #49] go/clear-text-logging in pkg/llmproxy/thinking/validate.go:173 #113 Implement API Version Header Support
• [CodeScanning #50] go/clear-text-logging in pkg/llmproxy/thinking/validate.go:194 #111 Implement Model Routing Rules
• [CodeScanning #50] go/clear-text-logging in pkg/llmproxy/thinking/validate.go:194 #110 Refactor internal/runtime Package
• [CodeScanning #51] go/clear-text-logging in pkg/llmproxy/thinking/validate.go:240 #109 Refactor internal/access Package
• [CodeScanning #52] go/clear-text-logging in pkg/llmproxy/thinking/validate.go:272 #108 Implement Alerting Rules
• [CodeScanning #51] go/clear-text-logging in pkg/llmproxy/thinking/validate.go:240 #106 Create Deployment Guide
• [CodeScanning #54] go/clear-text-logging in pkg/llmproxy/watcher/clients.go:60 #100 Implement Backup Strategy
• [CodeScanning #58] go/clear-text-logging in pkg/llmproxy/watcher/config_reload.go:122 #97 Implement API Key Management
• [CodeScanning #56] go/clear-text-logging in pkg/llmproxy/watcher/clients.go:116 #96 Implement Webhook Notifications
• [CodeScanning #59] go/clear-text-logging in sdk/cliproxy/auth/conductor.go:2171 #95 Implement Usage Statistics API
• [CodeScanning #57] go/clear-text-logging in pkg/llmproxy/watcher/clients.go:117 #94 Implement Account CRUD API

Low Priority

• [CodeScanning #45] go/clear-text-logging in pkg/llmproxy/thinking/apply.go:236 #121 Implement Batch Request API
• [CodeScanning #45] go/clear-text-logging in pkg/llmproxy/thinking/apply.go:236 #120 Add Developer Sandbox Mode
• [CodeScanning #46] go/clear-text-logging in pkg/llmproxy/thinking/apply.go:264 #118 Implement Content Moderation Hook
• [CodeScanning #48] go/clear-text-logging in pkg/llmproxy/thinking/apply.go:280 #114 Implement Data Export/Import
• [CodeScanning #49] go/clear-text-logging in pkg/llmproxy/thinking/validate.go:173 #112 Implement Log Aggregation
• [CodeScanning #53] go/clear-text-logging in pkg/llmproxy/thinking/validate.go:370 #107 Implement Distributed Tracing

Refactoring

• [CodeScanning #60] go/clear-text-logging in sdk/cliproxy/auth/conductor.go:2171 #93 Refactor Codex Translator

---

Action: These issues have been identified from the legacy repo. Please review and create new issues in this repo as needed, or close this issue if no action is required.

This migration issue was auto-generated.