gateway icon indicating copy to clipboard operation
gateway copied to clipboard

Feature Request: Support for Configuration Files in Portkey's AI Gateway

Open levie-vans opened this issue 6 months ago • 2 comments

Hello Portkey Team,

I'm currently using the Portkey's AI Gateway for integrating various LLMs into my application. First off, I want to extend my appreciation for the excellent work you've done with the gateway. It's been a game-changer in terms of performance and ease of use.

However, I've encountered a limitation that I believe could be improved. Currently, the configuration for the AI Gateway is passed directly through the request header using the 'x-portkey-config' key. While this works, it's not the most convenient approach, especially when dealing with API calls that strictly adhere to the OpenAI standards and don't allow for easy modification of headers.

To improve this, I'd like to suggest the addition of support for external configuration files. This feature would allow users to define their configurations in a separate file, making it easier to manage and update settings without altering the codebase. It would be particularly helpful for scenarios where different environments (development, staging, production) require different configurations.

Here are a few key benefits I believe this feature would offer:

  1. Simplified Configuration Management: Keeping configurations in separate files makes it easier to maintain and understand.
  2. Environment-Specific Configurations: Facilitates the use of different settings for various deployment environments.
  3. Cleaner Code: Reduces the clutter in the main application code, leading to better readability and maintenance.
  4. Consistency with Industry Standards: Many developers are accustomed to managing configurations through external files, making this a familiar and welcome feature.
  5. Security Concerns: Including multiple keys directly within the code not only bloats the request headers but also raises potential security risks.

I understand that implementing this feature would require effort and resources, but I believe the long-term benefits to users like myself would be significant.

Thank you for considering this request. I'm looking forward to any updates, and I'm more than willing to provide further input or clarification if needed.

levie-vans avatar Jan 15 '24 02:01 levie-vans