- You should be the Workspace Admin to be able to see the GitOps sidebar item and add Git Provider.
- You should have an Azure account.
Step 1 - Setting up
- Go to Settings from the top nav bar, select GitOps under Integration, and then click Add a Git provider.
Azure DevOps. Both the Instance URL and Display name are pre-populated for you.
Step 2 - OAuth application info
- On Step 2, click Direct link you will be redirected to Azure DevOps to authorize Bytebase to access your Azure DevOps account.
Step 2.1 - Register an application
Fill in the form with the provided info on the Bytebase setup wizard.
- Application name: can be other names than
bb, as long as the organization admin can identify this application is for
- Homepage URL: can be other URLs than
- Authorization callback URL: begins with the
host:portwhere the Bytebase console is running, and followed by
/oauth/callback. This is the URI Azure DevOps uses to callback Bytebase during the OAuth flow
- Authorizied scopes: Find the checkboxes for
Project and team (read),
Build (read and execute)
Click the "Register application" button after filling the info on Azure and you will see a created application, then click on show to generate a new client secret:
Step 2.2 - Verify setup
Fill in the Application ID and Secret onto the corresponding fields on the Bytebase setup wizard:
After you click Next, Bytebase will kick off an OAuth flow to verify the setup. If you are not currently logged on Azure. You will be prompted to login to complete the OAuth.
Step 3 - Confirm and add
When everything is setup properly, you will be informed that the setup is correct. Click Confirm and add.
Now you have successfully added a Git provider, developers can now link their Bytebase projects with one of their owned repositories from this Git provider.