User Connections have replaced Integrations
To continue using Push to git functionality, each user will have to configure their git integration in User Connections and provide their own personal access token. This functionality is no longer limited to admins.
This feature may not be available by default and might need to be enabled upon request. Please contact your account manager for more information.
Git integrations for SqlDBM projects are managed through User Connections. While this article provides specific instructions for GitLab, the related article at the end of this post covers the rest of the common steps to configuring the integration.
Once the integration has been configured, see the related at the end of this post on pushing to git and the various ways of generating the files themselves.
To enable version control through the AWS Code Commit repository, you will need to create a Personal Access Token and link it with SqlDBM using the steps below.
Please make sure to initialize your repository by creating at least one file in the main branch (Readme.md for example).
1 . Go to AWS Code Commit. Create or choose an organization.
2. Create a User.
Go to: Access Management → Users
Ensure that Programmatic access is selected.
3. Make sure to copy the Access Key Id and Secret access key. CodeCommit doesn't store it, and you will not be able to see it again.
Secret access key must have read & write permissions or full access.
If you want to create pull requests while pushing, there should be no restrictions on creating a pull request for the user who created the token.
Note the expiration period. When it expires, the token will no longer be valid, and the integration will break.
4. Open the SqlDBM Account - User Connections - page in a different browser tab.
5. Choose the "AWS CodeCommit" option.
6. Enter Access Key Id and the Secret access key.
7. Open CodeCommit again and create a repository.
8.Copy the link with HTTPS.
9. Open SqlDBM "User Connections" with the specified token.
10. Specify the repository URL.
11. Unmark the checkbox if you don't need to create pull requests.
12. Done.
Notice, you can add links only to those repositories that are related to the organization under the specified Secret Access Key.
Project users will now see a "Push to Git" button on the Forward engineering page. It will become active after generating DDL or YAML scripts.
The same behavior in the DataOps page (alter script popup).
After a successful push request, find your script in the repository files:
Source -> Repositories -> Commits - there should be a commit with your SQL script.
Otherwise, if you selected the 'Create Pull Request' option in the Integration page, go to: Source -> Repositories -> Pull requests.
