Run a Daily TiDB Cloud CLI Workflow

This example follows a typical operator workflow across TiDB Cloud Starter and TiDB Cloud Filesystem.

Prerequisites

• Install ti and run ti configure.
• Ensure your organization has capacity for one Starter cluster and one Filesystem.

Step 1. Inspect current resources

ti db list-db-clusters --db-cluster-type starter --output text
ti fs list-file-systems --output text

Step 2. Create a Starter cluster

ti db create-db-cluster \
  --db-cluster-type starter \
  --db-cluster-name daily-demo \
  --dry-run

ti db create-db-cluster \
  --db-cluster-type starter \
  --db-cluster-name daily-demo \
  --wait

Record the returned cluster ID. Because --wait was set, the create command returns after the cluster is active. You can inspect it again later:

ti db describe-db-cluster \
  --db-cluster-id "<cluster-id>" \
  --output text

Step 3. Verify SQL access

ti db create-db-sql-users --db-cluster-id "<cluster-id>"
ti db execute-sql-statement \
  --db-cluster-id "<cluster-id>" \
  --read-only \
  --sql "SELECT CURRENT_TIMESTAMP AS checked_at" \
  --output text

Step 4. Create and use a Filesystem

export TI_FS_FILE_SYSTEM_ID="$(ti fs create-file-system --query file_system_id --output text)"

printf 'daily workflow\n' | ti fs copy-file \
  --from-stdin \
  --to-remote /notes/today.txt

ti fs list-files \
  --path /notes \
  --output text

The file in /notes/today.txt verifies that the explicitly selected resource is usable.

Step 5. Check for updates

Unmount active filesystems before applying an update. A check is always non-mutating:

ti update --check

Apply an update when appropriate:

ti update --dry-run
ti update

Cleanup

ti fs delete-file-system \
  --file-system-id "$TI_FS_FILE_SYSTEM_ID"

ti db delete-db-cluster \
  --db-cluster-id "<cluster-id>"

Deleting local TiDB Cloud CLI configuration is not a substitute for deleting remote resources.

Security notes

• Do not echo FS tokens or formatted database connection strings.
• Use unique automation prefixes and delete only resources created by that run.
• Preview destructive operations with --dry-run.

What's next

• TiDB Cloud Starter CLI Command Reference
• TiDB Cloud Filesystem CLI Command Reference