cloud: essential doc changes#23158
Conversation
ti-chi-bot
Bot
added
contribution
|
@qqqdan PTAL |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates TiDB Cloud documentation to reflect tier-specific feature changes, notably restricting branching, local file imports, Parquet imports, and certain export options to the Starter tier, while introducing the new Essential Connection exclusive model (rolling out July 1, 2026) and updating changefeed billing. Reviewer feedback highlights several style guide violations, recommending the use of active voice and present tense, correcting grammatical issues (such as missing prepositions, articles, and template variable spacing), ensuring terminology consistency by using {{{ .starter }}} instead of hardcoded text, and removing an obsolete section in the audit logging documentation.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
|
||
| You can store audit logs in the following locations: | ||
|
|
||
| - TiDB Cloud |
There was a problem hiding this comment.
Since you are removing TiDB Cloud as a storage location for audit logs, please note that the section ## Access audit logging with TiDB Cloud Storage (lines 359-397) later in this file is now obsolete and should also be removed or updated in this PR.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
| </div> | ||
| </SimpleTab> | ||
|
|
||
| The Essential Connection exclusive model rolls out to new users in phases starting July 1, 2026. It supports standalone endpoints, which eliminates the need to include the account prefix when connecting. To create an AWS Endpoint Service private link connection using the exclusive model, on the same **Networking** page, in the **AWS Private Endpoint for External Services** area, click **Create Private Endpoint for External Services**, enter the required information, and then create the connection. |
There was a problem hiding this comment.
Not sure why this paragraph is placed here in this doc. Are there any subsequent sections?
qiancai
added
translation/no-need
ti-chi-bot
Bot
removed
the
missing-translation-status
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
2 participants
First-time contributors' checklist
What is changed, added or deleted? (Required)
Essential v2 changes doc.
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?