Add support for authenticating with gargle to chat_gemini() #320
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit expands `chat_gemini()` to support non-API key authentication, very similar to what we've done for other cloud providers. As a bonus I threw in viewer-based credential support for Connect. I don't have an environment to test this out yet, so this is mostly conjectural. Closes #317. Signed-off-by: Aaron Jacobs <[email protected]>
hadley
reviewed
Feb 12, 2025
| if (nchar(provider@api_key)) { | ||
| req <- req_headers_redacted(req, "x-goog-api-key" = provider@api_key) | ||
| } else { | ||
| # TODO: Can use req_headers_redacted() when !!! is supported. |
There was a problem hiding this comment.
Actually once we bump to the next version of httr2, req_headers() will auto-redact Authorization.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit expands
chat_gemini()to support non-API key authentication, very similar to what we've done for other cloud providers.As a bonus I threw in viewer-based credential support for Connect.
I don't have an environment to test this out yet, so this is mostly conjectural.
Closes #317.