Managing asset promotion with Git
If you have multiple instances of IBM Software Hub, you can use web-based Git repositories, such as GitHub and GitLab, to manage assets across environments.
You can use Git to maintain a single source of truth for assets across different instances. For example, you can use Git to move changes from development environments to staging environments to production environments.
You can use Git to manage assets from the following services:
- Data Virtualization
- IBM Knowledge Catalog
- IBM Knowledge Catalog Premium
- IBM Knowledge Catalog Standard
Prerequisites
An instance administrator must complete Enabling Git integration for asset promotion before you can manage asset promotion with Git.
Supported repositories
- GitHub
- GitHub Enterprise
- GitLab
- GitLab Self-Managed
Required permissions
To promote assets between environments you must have the following permissions in IBM Software Hub:
| Permission | Description |
|---|---|
| Push to Git | This permission is required to push changes to the remote Git repository. |
| Sync from Git | This permission is required to pull changes from the remote Git repository. |
If you don't know what permissions you have in IBM Software Hub, see Checking your permissions.
In addition, you must have the following permissions:
- Data Virtualization
- You must have the Data Virtualization Admin role on the service instances where you plan to manage assets using Git.
- IBM Knowledge Catalog
- You must have one of the following permissions in IBM Software
Hub:
- Administer platform
- Manage data protection rules