Reltio tenant and Git repository connections
Learn how the integrated development experience connects to a Reltio tenant, a Reltio tenant that uses Git, or a Git repository, and how to choose between them.
The integrated development experience gets your business configuration from a Reltio tenant or from a Git repository. Choose the connection that matches how your team works:
Reltio tenant: Get, edit, and apply the configuration yourself. Optionally, connect the Reltio tenant to a Git repository to track its configuration.
Git repository: Work with configuration stored in a Git repository.
The following table compares the three connections:
| Reltio tenant | Reltio tenant connected to Git | Git repository | |
|---|---|---|---|
| Connection option | Connect your Reltio Tenant | Connect your Reltio Tenant, then Connect to Git | Connect your Repository |
| Connects to | A Reltio tenant | A Reltio tenant and a branch of a remote Git repository | A Git repository |
| Reltio sign-in | Required | Required | Not required |
| Get configuration from a Reltio tenant | Available | Available | Not available |
| Apply changes to a Reltio tenant | From the integrated development experience | From the integrated development experience or through your deployment pipeline | Through your deployment pipeline |
| Configuration history | Available | Available | Not available |
| Git | Not used | Used for the configuration of the Reltio tenant | Always used |
The following figure shows how configuration moves between the Reltio tenant, the integrated development experience, and the Git repository for each connection:
Work directly with a Reltio tenant
Connect to a Reltio tenant when you want to get, edit, and apply its configuration yourself. Connecting the Reltio tenant to Git is optional. To start, see Connect to a Reltio tenant.
Add Git to a Reltio tenant connection
Connect a Reltio tenant to Git when you want to track configuration changes, review them in pull requests, and promote them between Reltio tenants. Connecting to Git gives you the following benefits:
Trace each change: Find the author and the reason for every configuration change.
Review before it reaches a Reltio tenant: Check a change in a pull request.
Work safely: Prepare a change in a feature branch without affecting the configuration that others use.
Promote changes: Move a tested change from one Reltio tenant to another by merging branches.
The integrated development experience still gets the configuration from the Reltio tenant. Git tracks the configuration and does not supply it.
Keep several Reltio tenants in one remote Git repository, each on its own branch, such as dev, test, and prod. To promote changes between Reltio tenants, use one Git repository for all of them. The committed files contain neither the environment name nor the Reltio tenant ID, so Business Config/BusinessConfig.json has the same path on every branch. A pull request from dev into test therefore shows exactly what differs between the two Reltio tenants.
To connect a Reltio tenant to Git, see Connect or disconnect a Reltio tenant to Git repository. To work with branches, see Work with branches and promote changes between Reltio tenants.
Work from a Git repository
Connect to a Git repository when your team keeps configuration in Git and deploys it through a pipeline. To start, see Connect to a Git repository.
Use a Reltio tenant connected to Git and a Git repository on one team
An administrator connects each Reltio tenant to Git, so that the configuration of each Reltio tenant is on its own branch. Other team members select Connect your Repository to connect to that Git repository, edit the configuration, and open pull requests. The deployment pipeline applies the merged changes to each Reltio tenant.
Agree on one way to apply changes to each Reltio tenant, either from the integrated development experience or through a deployment pipeline, so that changes do not overwrite each other. You can connect to a Reltio tenant and to a Git repository in the same workspace.