Feature/Add support for per-request metadata/headers #704
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
PR introduces support for setting per-request metadata/headers in GenerativeModel.generate_content. Previously, headers could only be set at the client configuration level using default_metadata, making it difficult to specify user-specific headers dynamically for each request. This enhancement improves flexibility, particularly for integrations with proxy services like Helicone that require user-specific headers.
Technical
Added a new parameter
extra_headers: dict[str, str] | None
.Ensured that
extra_headers
are properly merged with existing request metadata.Preserved backward compatibility by making extra_headers optional.
Updated function documentation to reflect the new parameter.
closes #698