cloud: document Premium import workflows #21968

alastori · 2025-10-25T01:16:30Z

What is changed, added or deleted? (Required)

add an Amazon S3 import guide tailored to TiDB Cloud Premium
align MySQL CLI, CSV import, and migration docs with the new Premium workflow
document IAM role creation via the CloudFormation helper and manual fallback

Which TiDB version(s) do your changes apply to? (Required)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s):

Do your changes match any of the following descriptions?

Delete files
Change aliases
Need modification after applied to another branch
Might cause conflicts after applied to another branch

gemini-code-assist · 2025-10-25T01:16:46Z

Summary of Changes

Hello @alastori, 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 expands the documentation for TiDB Cloud Premium, focusing on various data import and migration strategies. It introduces new guides for importing CSV data from Amazon S3 and Alibaba Cloud OSS, details how to use the MySQL Command-Line Client for data imports, and provides a comprehensive workflow for migrating data from self-managed TiDB clusters to TiDB Cloud Premium. A key aspect of these new documents is the clear instruction on configuring IAM roles for secure cloud storage access, offering both automated CloudFormation and manual setup options.

Highlights

New S3 Import Guide: A dedicated Amazon S3 import guide tailored for TiDB Cloud Premium has been added.
Premium Workflow Alignment: Existing documentation for MySQL CLI, CSV import, and general migration processes has been updated and aligned with the new TiDB Cloud Premium workflows.
IAM Role Documentation: Detailed instructions for creating necessary IAM roles, including a CloudFormation helper and manual fallback steps, are now documented for cloud storage access.

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.

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 introduces comprehensive documentation for TiDB Cloud Premium import workflows, covering CSV imports, MySQL CLI usage, S3 integration, and migration from self-managed TiDB. The new documents are well-structured and detailed. My review focuses on improving clarity, correcting minor grammatical and technical errors, and ensuring consistency with the repository's style guide. I've provided specific suggestions to enhance readability and accuracy.