community: add new parameter default_headers

[lu-ohai]

Thank you for contributing to LangChain!

• PR title: "package: description"

  • "community: 1. add new parameter default_headers for oci model deployments and oci chat model deployments. 2. updated k parameter in OCIModelDeploymentLLM class."

• PR message:

  • Description: 1. add new parameters default_headers for oci model deployments and oci chat model deployments. 2. updated k parameter in OCIModelDeploymentLLM class.

• Add tests and docs:

  1. unit tests
  2. notebook

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
langchain	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 18, 2024 10:33pm

[efriis]

one question /suggestion to remove the route from headers. otherwise looks good.

Also, if you're interested in maintaining this integration without us in the loop, we'd love to get an integration package out! Future PRs against langchain would just be {docs updates, as well as registering your package in libs/packages.yml, deprecating this community integration in favor of your integration package}

Here's the guide, and if you have questions, feel free to leave them in the comments on those pages so others can see them! https://python.langchain.com/docs/contributing/how_to/integrations/

There's some folks within oracle working on this that may be interested in collaborating

[efriis]

should this be included as a header?

[mrDzurb]

Hi @efriis, thank you for your comment! In the current implementation of OCI Model Deployment, the route parameter needs to be passed through the header. For text and chat models, this parameter will be hardcoded by default. However, users can modify the value of the route parameter if needed by utilizing the default_header attribute.

[efriis]

sounds good

[mrDzurb]

one question /suggestion to remove the route from headers. otherwise looks good.

Also, if you're interested in maintaining this integration without us in the loop, we'd love to get an integration package out! Future PRs against langchain would just be {docs updates, as well as registering your package in libs/packages.yml, deprecating this community integration in favor of your integration package}

Here's the guide, and if you have questions, feel free to leave them in the comments on those pages so others can see them! https://python.langchain.com/docs/contributing/how_to/integrations/

There's some folks within oracle working on this that may be interested in collaborating

Hi @efriis, moving to the integration package is already on our roadmap! Thanks!