Set up the private content repository feature.
When you set up a remote repository, you can add any private content repository that is Git-based, including GitHub, GitLab, and Bitbucket. Also, On-prem repositories are supported.
Although you can set up multiple development tenants, in a cluster of tenants that includes one production tenant and one or more development tenants, only one development tenant can push content. 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 development tenant that has been installed 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.
If the content repository option is disabled for the production or development tenant, the tenant becomes standalone and does not push or pull content.
Once the development tenant is set up, you can only change content repository settings within the tenant.
Use case scenarios for a private remote repository
The following are typical scenarios for setting up a private remote repository for the production and one or more development tenants.
New development tenant and new or existing production tenant
The production tenant is first activated as a standalone (by default), and the private remote repository is then enabled in the production tenant. Once enabled, the first development tenant becomes the push tenant, the production tenant becomes a pull tenant, and any additional tenants need to set to pull tenants.
Existing development and production tenants
The production and development tenants were managed in parallel with different sets of content.
Before you begin
Verify that you have network connectivity from Cortex XSOAR to the private remote repository. All communication goes through Cortex XSOAR, so it must have access to the remote repository. If direct access from Cortex XSOAR is not enabled you can use engines with access to the repository.
If you are changing your remote repository settings, back up existing content to your local computer by navigating to Export all custom content.
→ → → → and clickYou must have Instance Administrator or Account Admin permission.
Download and install the development image file. For more information, see Step 3. Set up a remote repository.
How to set up a private remote repository
Perform the following procedures in the order listed below to set up a private remote repository.
Note
When the first tenant (development or production) is enabled for the remote repository, the content from that tenant automatically populates the repository. When you first enable additional tenants (development or production) to the same remote repository, you will see the Specified repository is not empty window and have the option to use the content in the remote repository or replace the content with content from the new tenant.
These instructions describe enabling the production tenant first, so the remote repository will initially contain production tenant content. You can enable a development tenant first if you want the remote repository to initially contain the content from the development tenant.