Forward params not in the provider config keys - Githubissues

Portkey-AI / gateway

A Blazing Fast AI Gateway with integrated Guardrails. Route to 200+ LLMs, 50+ AI Guardrails with 1 fast & friendly API.

https://portkey.ai/features/ai-gateway

MIT License

6.34k stars 454 forks source link

Forward params not in the provider config keys #719

Closed narengogi closed 3 weeks ago

narengogi commented 3 weeks ago

… Title:

transformToProviderConfig has been looping over the provider config and setting keys, Flipped it to loop over request params

Motivation: (optional)

To forward any params not specified in the config without transformation

Related Issues: (optional)

issue-number

Testing done

[X] Tested when transform object is a recursive array
[X] Tested nested properties
[X] Tested value as 'default'
[X] Tested when required and default is available
[X] Tested remaining routes for sanity

Note I've not added support for min and max

narengogi commented 3 weeks ago

Closing this after discussing with @VisargD @roh26it @ayush-portkey

summary:

These changes are not backward compatible if clients have already been sending additional parameters and they've been getting ignored till now
This will restrict dynamic-routing/fallbacks between providers requiring users to override params to null or undefined instead of forwarding them (@VisargD)