Tutorial: Deploy Schema Change with Rollout Policy

While you can not self-approve your own created issue, once the issue is approved by the others, you can roll out your own issue if qualified.

Workspace Admin or DBA can configure the Rollout policy for a particular environment from the Environment detail page:

This setting will affect projects using either UI workflow or GitOps workflow. The rollout policy determines who will rollout the database changes.

​
Automatic rollout

If automatic option is checked, Bytebase will roll out the change automatically if all check have passed. Unpassed checks will block the automatic rollout and require manual intervention:

​
Manual rollout by dedicated roles

If any roles are specified, Bytebase requires users with those roles to manually roll out the change.

​
Manual rollout with custom approval flow

Bytebase requires the last approver from the activated custom approval flow to roll out the change manually.

Tutorial: Deploy Schema Change with Rollout Policy

While you can not self-approve your own created issue, once the issue is approved by the others, you can roll out your own issue if qualified.

Workspace Admin or DBA can configure the Rollout policy for a particular environment from the Environment detail page:

This setting will affect projects using either UI workflow or GitOps workflow. The rollout policy determines who will rollout the database changes.

​
Automatic rollout

If automatic option is checked, Bytebase will roll out the change automatically if all check have passed. Unpassed checks will block the automatic rollout and require manual intervention:

​
Manual rollout by dedicated roles

If any roles are specified, Bytebase requires users with those roles to manually roll out the change.

​
Manual rollout with custom approval flow

Bytebase requires the last approver from the activated custom approval flow to roll out the change manually.