You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to test the Databricks and Snowflake Models with LiteLLM proxy, but it seems that in the case of for example databricks I am forced to set a DATABRICK_API_KEY and DATABRICKS_API_BASE as config variables. This does not allow me to define different models using different accounts of Databricks right? And I believe is the same with Snowflake.
Is there a way to set DATABRICK_API_KEY and DATABRICKS_API_BASE on the Model itself and not using global variables?
Likewise with SNOWFLAKE_JWT and SNOWFLAKE_ACCOUNT_ID.
Ideally these 2 providers should be possible to configure like Google or Bedrock where you can have multiple models using different accounts configure no?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to test the Databricks and Snowflake Models with LiteLLM proxy, but it seems that in the case of for example databricks I am forced to set a DATABRICK_API_KEY and DATABRICKS_API_BASE as config variables. This does not allow me to define different models using different accounts of Databricks right? And I believe is the same with Snowflake.
Is there a way to set DATABRICK_API_KEY and DATABRICKS_API_BASE on the Model itself and not using global variables?
Likewise with SNOWFLAKE_JWT and SNOWFLAKE_ACCOUNT_ID.
Ideally these 2 providers should be possible to configure like Google or Bedrock where you can have multiple models using different accounts configure no?
Thank you!!
Beta Was this translation helpful? Give feedback.
All reactions