feat(gateway): add debug logging with file storage and retention
feat(gateway): add audit logging for user actions
feat(gateway): add request ID tracking and rate limit headers
feat(gateway): add model aliases and load balancing strategies
feat(gateway): add config hot-reload via SIGHUP
feat(gateway): add CORS support
feat(gateway): add data export API and dashboard endpoints
feat(gateway): add dashboard pages for audit and debug logs
feat(gateway): add concurrent request limiting per token
feat(gateway): add streaming timeout support
feat(gateway): add migration support for new schema fields
The diff shows the deletion of three files that were part of the old litellm configuration and new-api setup:
1. `litellm/config.yaml` - Contains the old model configuration and fallback settings
2. `new-api/CHANNELS.md` - Documentation for channel configuration in new-api
3. `new-api/init-channels.sh` - Script to initialize new-api channels and tokens
These files are being removed as part of a refactor or migration away from the old setup pattern. The removal is a cleanup operation that removes the old configuration artifacts and associated setup scripts for the new-api system that was previously used for centralized model routing and channel management.
None of the changes require a breaking change notice as they are removing deprecated configuration files rather than introducing breaking changes.
The deletion of these files suggests a shift away from the previous litellm-based centralized model routing approach to a new system or configuration method. The removal of the init script also indicates that the automatic channel setup has been eliminated, likely replaced by a different approach to API key management and model routing.
