Git repository replication¶
This topic provides information about Snowflake support for replicating Git repository objects.
Before you get started, we recommend that you be familiar with Snowflake support for Git repositories. For more information, see Using a Git repository in Snowflake.
Considerations for replicating Git repositories¶
To replicate any Git repository objects that you’ve integrated with Snowflake, you specify the database or schema that contains the Git repository object in a replication group or a failover group. You don’t have to perform any separate step to enable replication for Git repositories.
The secrets from the primary system are replicated to the secondary system.
On the secondary system, you can read from the repository. However, you can’t commit, fetch from, or push to
the remote origin server from the secondary system. After you promote the secondary system to be the primary
by failing over, you can perform these other operations on the Git repository.
Although the Snowflake support for Git uses the term repository stage, the replication mechanism for Git repositories isn’t the same as for stages and other data pipeline objects. For example, you don’t have to configure directory tables to enable replication for Git repositories.
Snowflake supports replication for Git repositories up to 5 GB in size. Larger repositories currently aren’t supported.