mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-07-26 09:52:11 +03:00
2 lines
1.4 KiB
JSON
2 lines
1.4 KiB
JSON
{"author":{"id":"MDQ6VXNlcjQwODM4MTI=","is_bot":false,"login":"apoapostolov","name":"Apostol Apostolov"},"body":"## What\n\nA CLI command to rotate API keys across all configured providers:\n\n- `omniroute keys rotate` — Rotate all expired/soon-to-expire keys\n- `omniroute keys rotate <provider>` — Rotate keys for a specific provider\n- `omniroute keys status` — Show key health (age, expiry, last used)\n\n## Why\n\n- `api/settings/oneproxy/rotate` and MCP tool `omniroute_oneproxy_rotate` exist, but only for the OneProxy feature.\n- Many providers (especially Google Cloud, Azure, AWS) use rotating/temporary credentials. There's no generic rotation mechanism.\n- The `token-health` route and `api/providers/expiration` route already track expiration — a CLI command would make this actionable.\n- Key lifecycle management is a security best practice for any proxy handling multiple API keys.\n\n## Implementation\n\n- Extend the existing `api/keys/` and `api/providers/expiration` logic.\n- For OAuth-based providers (Google), trigger the OAuth flow or prompt for a refresh token.\n- Support env var fallback: `omniroute keys rotate OpenRouter --from-env OPENROUTER_API_KEY`.","comments":[],"createdAt":"2026-05-02T14:27:26Z","labels":[],"number":1881,"title":"[Feature] Generic API key rotation CLI command","url":"https://github.com/diegosouzapw/OmniRoute/issues/1881"}
|