GitOps with VCS Integration

Built-in GitOps


The built-in Bytebase GitOps workflow is opinionated for the typical use case:

  • It imposes a naming convention on the migration file.
  • It only creates Bytebase rollout issue when the migration file is merged into the target branch. Under the hood, it creates a webhook in the linked repository to observe the merge event.

You can check this demo issue to see what it looks like after the setup. This issue is created by Bytebase after the PR is merged.

The built-in GitOps setup contains 3 steps:

  1. Add Git Provider
  2. Add GitOps Connector in Project
  3. Create Migration Files

Custom GitOps with API

If the built-in workflow is not suitable, you can opt to Bytebase API to fully customize the GitOps workflow to integrate with your CI pipeline.

Edit this page on GitHub

Subscribe toΒ Newsletter

By subscribing, you agree with Bytebase's Terms of Service and Privacy Policy.