Skip to main content

git follower mode

The Omni git integration's follower mode allows you to centralize the development of a model and deploy it to multiple regions like the US and EU, or develop models using a SDLC (Software Development Lifecycle) approach.

How it works​

Follower mode works by specifying one Omni model as a leader and another model as a follower. The follower is updated when changes occur to the leader, allowing you to create a clear separation between models without manual intervention or the risk of drift.

  • All development happens in the leader, against its own git base branch
  • The follower is read-only, meaning direct changes can't be made to the model
  • Promotion to the follower happens only by creating a pull request that merges changes from leader's base branch into the follower's base branch. Once merged, Omni automatically applies the changes to the follower model.

Use cases​

Follower mode is useful for:

Development & production environments​

This approach allows you to implement a permanent SDLC solution, where you develop against one model (the leader) and then promote vetted changes to production (the follower). This ensures that the production model used to build content remains stable, consistent, and protected from ad-hoc changes.

Multi-region or organization deployment​

In these cases, you may be subject to regulations that restrict where your data can reside. Instead of manually applying changes to multiple models, you can use follower mode to develop against one model (the leader) and then set up followers that will automatically absorb the changes.

Model requirements​

Follower mode should only be used with models that:

  • Have the same underlying schema structure, and
  • Are kept in sync (schema refreshes)

Models do not need to be in the same database connection or even the same Omni organization.

Setup & best practices​

Ready to get started?