Add GCS connector documentation and assets

[Kushagra1122]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @Kushagra1122, 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 introduces comprehensive documentation for the Google Cloud Storage (GCS) connector, designed to facilitate seamless integration of GCS buckets with PipesHub. The new documentation provides users with detailed instructions on authentication using service accounts, configuring sync strategies, applying various data filters, and understanding data sync behaviors. It also includes extensive troubleshooting guides and frequently asked questions to ensure a smooth setup and operational experience, ultimately enabling AI-powered search and organization-wide access to GCS content.

Highlights

• New GCS Connector Documentation: A comprehensive documentation file for the Google Cloud Storage (GCS) connector has been added, detailing its features, configuration, and usage within PipesHub.
• Detailed Configuration Guide: The new documentation includes a step-by-step guide for setting up the GCS connector, covering service account creation, permission grants, key management, and PipesHub configuration.
• Sync Behavior and Filtering Options: Information on initial and incremental sync processes, permission handling, sync frequency, and various filtering options (bucket names, file extensions, modified/created dates) is now available.
• Troubleshooting and FAQs: Extensive troubleshooting tips for common issues like authentication failures, access denied errors, and sync problems, along with a detailed FAQ section, have been included to assist users.
• Documentation Navigation Update: The docs.json file has been updated to integrate the new GCS connector documentation into the main navigation structure.

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 comprehensive documentation for the GCS connector. The content is detailed and covers setup, features, and troubleshooting effectively. My review focuses on improving the document's structure and readability. I've identified a few areas for improvement, including fixing the document hierarchy by correcting heading levels, addressing a structural issue with accordions that hides most of the content, removing duplicated information, and ensuring consistent formatting for technical terms. These changes will enhance the usability and maintainability of the documentation.