DEV Community

Cover image for Database Change Management with Amazon Aurora and GitHub

Posted on

Database Change Management with Amazon Aurora and GitHub

This is a series of articles about Database Change Management with Amazon Aurora

In the last article Database Change Management with Amazon Aurora, you have tried UI workflow in Bytebase.

This tutorial will bring your Amazon Aurora schema change to the next level by introducing the GitOps workflow, where you commit the schema change script to the GitHub repository, which will in turn trigger the schema deployment pipeline in Bytebase.

You can use Bytebase free version to finish the tutorial.

Features included

  • GitOps Workflow
  • Change History


Before you start this tutorial, make sure you have the following ready:

  • Followed our previous UI-based change tutorial Database Change Management with Amazon Aurora.
  • An Amazon Aurora MySQL instance.
  • A GitHub account.
  • A public GitHub repository, e.g  aurora-test-bb-local.
  • Docker installed locally.
  • An ngrok account. (ngrok is a reverse proxy tunnel, and in our case, we need it for a public network address in order to receive webhooks from GitHub. We use ngrok here for demonstration purposes. For production use, we recommend using Caddy.)


Step 1 - Run Bytebase in Docker with URL generated by ngrok

To make local-running Bytebase visible to GitHub, we’ll pass the URL generated by ngrok to --external-url.

  1. Login to ngrok Dashboard and follow its Getting Started steps to install and configure.

  2. Run

ngrok http 5678
Enter fullscreen mode Exit fullscreen mode

and obtain the public URL:

  1. Make sure your Docker daemon is running, if it’s running Bytebase container for the previous tutorial, stop and remove it. The data created in the last tutorial is stored under ~/.bytebase/data by default and will be restored if the system restarts.

  2. Start the Bytebase Docker container by typing the following command in the terminal. Pay attention to the last parameter --external-url, which is generated by ngrok.

docker run --init \
--name bytebase \
--platform linux/amd64 \
--restart always \
--publish 5678:8080 \
--health-cmd "curl --fail http://localhost:5678/healthz || exit 1" \
--health-interval 5m \
--health-timeout 60s \
--volume ~/.bytebase/data:/var/opt/bytebase \
bytebase/bytebase:1.13.0 \
--data /var/opt/bytebase \
--port 8080 \
Enter fullscreen mode Exit fullscreen mode
  1. Bytebase is running successfully in Docker, and you can visit it via docker

Step 2 - Find your Amazon Aurora in Bytebase

  1. Visit Bytebase Console through the browser via your ngrok URL Log in using your account created from the previous tutorial.

  2. If you followed the previous tutorial, you should see that the project and database created are still in your workspace.

Step 3 - Connect Bytebase with

  1. Click Settings on the top bar, and then click Workspace > GitOps. Choose and click Next.


  1. Follow the instructions within STEP 2, and in this tutorial, we will use a personal account instead of an organization account. The configuration is similar.

  2. Go to your GitHub account. Click your avatar on the top right, and then click Settings on the dropdown menu.

  3. Click Developer Settings at the bottom of the left sidebar. Click OAuth Apps, and add a New OAuth App.

  4. Fill Application name and then copy the Homepage and Authorization callback URL in Bytebase and fill them. Click Register application.

  5. After the OAuth application is created, click Generate a new client secret. Copy the Client ID and the newly generated Client Secret, paste them back into Bytebase's Application ID and Secret.

  6. Click Next. You will be redirected to the confirmation page. Click Confirm and add, and the Git provider is successfully added.

Step 4 - Enable GitOps Workflow with Amazon Aurora

  1. Go to your project TestAurora, click GitOps, and choose GitOps Workflow. Click Configure GitOps.

  2. Choose - the provider you just added. It will display all the repositories you can manipulate. Choose aurora-mysql-test-bb-local.

  3. Keep the default setting, and click Finish.

Step 5 - Change schema for Amazon Aurora by pushing SQL schema change files to GitHub

  1. In your GitHub repository aurora-mysql-test-bb-local, create a folder bytebase, then create a subfolder Test, and create a SQL file using the naming convention
Enter fullscreen mode Exit fullscreen mode

It is the default configuration for the file path template setting under project TestAurora > GitOps.

Paste the sql script in it.

   course VARCHAR(255)
Enter fullscreen mode Exit fullscreen mode


  1. Commit and push this file.

  2. Go to Bytebase, and go into project TestAurora. You’ll find there is a new Push Event and a new issue 107 created.

  3. Click issue/107 and go the issue page. Click Resolve issue, and the issue will be Done. You’ll see:

    • The issue is created via
    • The issue is executed without approval because it’s on Test environment where manual approval is skipped by default. The Assignee is Bytebase, because the execution is automatic, and requires no manual approval.
    • The SQL is exactly the one we have committed to the GitHub repository.
    • The Creator is A, because the GitHub user you use to commit the change has the same email address found in the Bytebase member list.


  1. Click View change, you can view the schema diff.

  2. Go to GitHub repository, and you will see besides your committed sql, there is a .db_demo##LATEST.sql file. Because you have configured Schema path template before, Bytebase will write back the latest schema to that specified path after completing the schema change. Thus you have access to an update-to-date full schema at any time.

Summary and What's Next

Now that you have tried the GitOps workflow, which stores your Amazon Aurora schema in GitHub and triggers the change upon committing change to the repository, to bring your Amazon Aurora change workflow to the next level of Database DevOps - Database as Code.

You can check out GitOps docs to learn more configuration details.

In the real world, you might have separated feature and main branches corresponding to your development and production environment, you can check out GitOps with Feature Branch Workflow to learn the setup. Have a try and look forward to your feedback!

Top comments (0)