Adding Custom OPENAI API URL Configuration Option

[yszve]

Description of the new feature / enhancement

I would like to request an enhancement to the OPENAI API KEY configuration section. Currently, the application only allows the user to input the API KEY but does not support setting a custom API URL.

Scenario when this would be used?

The ability to set a custom OPENAI API URL would be particularly useful in the following scenarios:

Corporate environments: Many companies use internal networks and API proxies for security and compliance reasons. Allowing the configuration of a custom API URL enables these users to route their requests through internal gateways.

Testing and Development: Developers often work in multiple environments, such as development, staging, and production, each with its own API endpoints. Having the ability to switch between these endpoints seamlessly would greatly enhance the development workflow.

Regional Restrictions: In regions where access to specific URLs might be restricted, being able to use alternate endpoints can ensure uninterrupted service availability.

Supporting information

No response

[htcfreek]

/dup #32960

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!