Creating a development tenant automatically creates a private content repository. Activate the content repository feature on the production tenant.
When you set up a remote repository, you can either use the Cortex XSOAR built-in remote repository, or you can add any private content repository that is Git-based, including GitHub, GitLab, and Bitbucket. In addition, on-premise repositories are also supported.
Considerations
When you activate a tenant and enable the content repository in Cortex Gateway, Cortex XSOAR by default uses the the built-in repository. The built-in remote repository requires fewer configurations than using a private remote repository and cannot be accessed directly. If you want to use a private remote repository, you need to configure it when you enable the remote repository in the tenant.
In a cluster of tenants that includes one production tenant and one or more development tenants, only one development tenant pushes. The production tenant and any other development tenants pull from the one development tenant that is configured to push content. After the remote repository is enabled in the production tenant, by default the first activated development tenant is set to push content to the remote repository. When you create additional development tenants, they are set to pull content from the remote repository.
For a simple one-branch deployment, we recommend using the built-in repository. If you want to use multiple branches, or if you need access to the content repository outside the Cortex XSOAR platform (for example to implement some scanners) you must use a private repository.
If you want to use a private remote repository with one or more branches, you need to enable the remote repository in each tenant and then set up all branches in the remote repository configuration page in Cortex XSOAR.
If the content repository option is disabled for the production or development tenant, the tenant becomes standalone and does not push or pull content.
Activation may take some time. You should receive notification by email that the production or development tenant has completed the activation process.
Once the activation completes, you can only change content repository settings within the tenant.
Before you Begin
If you are changing your remote repository settings, back up existing content to your local computer by navigating to → → → → and click Export all custom content.
You must have Instance Administrator or Account Admin permission.