CloudDM 4.8.0 adds GreptimeDB as a DataSource
Skip to main content

Changes

A change is the smallest unit of database CI/CD execution in CloudDM.

Change list​

  1. Sign in to the CloudDM console.
  2. Open CI/CD in the sidebar to view the change flow list.
  3. Open the target flow and click Change Records.
  4. Search by change name. The list shows the status, change name, time, Git Ops integration, stage, and available actions.

Change details​

An ordinary change progresses through Submit → SQL Review → Work Order Approval → Execute.

  • Submit retrieves SQL from the repository and compares it with the existing snapshot. If there is no new SQL, the change moves to Change Closed.
  • SQL Review checks new SQL against the security rule assigned to the target database's environment. See Assign a security rule to an environment.
  • Work Order Approval uses the execution configuration to decide whether to start ticket approval. Approval Process shows approval information and a link to the associated ticket.
  • Execute runs SQL automatically or waits for a user to choose an execution method, depending on the flow settings.

When you build a snapshot, the record progresses through Submit → Snapshot Change.

The change details page has these tabs.

  • SQL Changes offers a result view and a Diff view. The result view collects new SQL and labels each source file. The Diff view compares file contents before and after the change.
  • SQL Review shows the SQL, check results, and any rule violations.
  • Approval Process shows ticket approval progress and links to the ticket details.
  • Change Execution shows execution tasks, SQL, status, and logs.

Confirm SQL review​

The SQL Check setting in the execution configuration determines whether a user needs to confirm the review.

  1. For a change waiting on SQL review, open its SQL Review tab.
  2. Review the SQL and the rule check results.
  3. If the change should proceed, use the skip-check action at the top of the page. With check errors, the action is labeled Skip.
info

After fixing the SQL and committing it to the repository, the configured webhook can trigger CloudDM to fetch the updated code and check it again. You can also trigger the change another way.

Retry a change​

If a change encounters an error, click Retry in the upper-right corner of its details page. If the approval stage needs a new ticket, the action is Reinitiate Work Order.

Execute a change​

If the execution configuration uses Manual, the flow pauses at the execution stage for you to choose an action.

  • Done Manually records SQL execution you completed directly in the database. Click Close Ticket, then Confirm Completion.
  • Execute now starts SQL execution immediately.
  • For scheduled execution, select a time and click Execution At Time.

During execution, check task status, SQL, and logs. Depending on the task status, you can pause, resume, retry, terminate, skip, or cancel a skip.