|
2 | 2 | title: Plan |
3 | 3 | --- |
4 | 4 |
|
5 | | -A **Plan** is the core component of Bytebase’s CI/CD pipeline. It defines a series of schema or data changes to be applied to one or more databases. |
| 5 | +A **Plan** is the core component of Bytebase’s CI/CD pipeline. It defines a series of schema or data changes to be applied to one or more databases. It can be converted into an **Issue** for review and deployment. |
6 | 6 |
|
7 | | -### 1. Create a New Plan |
| 7 | +### 1. Create Plan |
8 | 8 |
|
9 | | -In your project, go to **CI/CD** > **Plans** in the left menu and click **+ New Plan**. |
| 9 | +In your project, navigate to **CI/CD** > **Plans** and click **+ New Plan**. |
10 | 10 |
|
11 | | -### 2. Select Target Databases |
| 11 | +### 2. Select Databases |
12 | 12 |
|
13 | | -Choose one or more databases where the changes will be applied. Click **Confirm** to proceed. |
| 13 | +Choose one or moretarget databases and click **Confirm**. |
14 | 14 |
|
15 | 15 | ### 3. Add Changes |
16 | 16 |
|
17 | | -Add SQL statements (multiple allowed). Click **Create** to convert the plan into an issue. SQL review runs automatically, showing any warnings. |
| 17 | +Add SQL statements (multiple allowed by clicking **+ Add Change**) and click **Create**. The plan becomes an issue with automatic SQL review. |
18 | 18 |
|
19 | 19 |  |
20 | 20 |
|
21 | | -### 4. Submit for Review waiting for approval (Enterprise) |
22 | | -s |
23 | | -Click **Ready for Review** to submit it for approval. The issue awaits approval per [configured rules](/change-database/approval). |
| 21 | +### 4. Submit for Review (Enterprise) |
| 22 | + |
| 23 | +Fix the warning, and click **Ready for Review**. Approval follows [configured rules](/change-database/approval). |
24 | 24 |
|
25 | 25 |  |
26 | 26 |
|
27 | | -### 5. Deploy to Environments |
| 27 | +### 5. Deploy |
28 | 28 |
|
29 | | -Once approved, go to the **Rollout** section to begin deployment. |
| 29 | +After approval, go to the **Rollout** section to deploy changes. You may configure the rollout policy to `Automatic` in the [environment](/change-database/environment-policy/rollout-policy). |
30 | 30 |
|
31 | 31 |  |
32 | 32 |
|
33 | | -First, deploy to the `Test` environment. If successful, proceed to deploy to `Prod`. |
| 33 | +Deploy to `Test` first, then `Prod` after success. |
0 commit comments