Branching

Omnata has been designed from the ground up for robust change management, with configuration branching strategies to match a variety of common scenarios.

Branching is available for both inbound and outbound syncs, but naturally it works quite differently in each case. See the pages beneath this one to learn more about each.

That said, there's a key ground rule that's important to keep in mind:

The main branch is always production

People use git branches in a wide variety of ways. Omnata branching is much simpler and restrictive (in a good way).

Every Sync has an implied "main" branch, which is for the production usage of the app (the part that impacts day to day business activities). All branches are intended for testing changes in advance of applying them to the main sync.

When there are multiple Snowflake accounts in use, branching is not used.

Instead, syncs are created as multi-account and the same sync configuration is applied across the different Snowflake accounts.