Feaaure/google drive vertex credentials

[davehamptonusa]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @davehamptonusa, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly upgrades the Google Drive document loader by integrating robust support for Google Vertex (Service Account) credentials. This enhancement provides users with more flexible and secure authentication options when accessing Google Drive files. The changes encompass new and refined input parameters for better control over shared drives and folders, a refactored backend to seamlessly manage different authentication flows, and UI improvements to guide users during Vertex credential configuration. A new comprehensive test suite ensures the reliability and correctness of these new features.

Highlights

• Google Vertex Credentials Support: The Google Drive document loader now supports Google Vertex (Service Account) credentials, in addition to the existing OAuth2, offering more flexible authentication options.
• Enhanced Drive Integration: New input fields like 'Shared Drive ID' are introduced, and existing fields such as 'Folder ID' and 'Include Shared Drives' are updated to provide more granular control and better support for shared drives, particularly when using service accounts.
• Dynamic Authentication Handling: The backend logic has been refactored to dynamically determine and handle the appropriate authentication method (OAuth2 or Service Account) for all Google Drive file operations.
• UI/UX Improvements for Vertex: The user interface now automatically enables and disables the 'Include Shared Drives' option when a Google Vertex credential is selected for a Google Drive node, ensuring correct configuration and preventing user errors.
• Comprehensive Testing: A new dedicated test file (GoogleDrive.test.ts) has been added to thoroughly validate the new credential types, input field configurations, authentication detection, and required field validations for both OAuth2 and service account methods.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds support for Google Vertex AI (Service Account) credentials to the Google Drive document loader, in addition to the existing OAuth2 method. The changes are extensive, refactoring many of the core methods to handle both authentication paths. The backend logic is supported by new unit tests and corresponding UI adjustments to manage the new input fields. My review focuses on a critical syntax error in the UI code, opportunities to refactor duplicated logic for better maintainability, and minor improvements to error messages and code clarity.