To work with the remote repositories, you must have one machine configured as your development machine, and the main account configured as your production environment.
Prerequisites
Before configuring the remote repository, review the following list of prerequisites:
Ensure that the Selective Propagation feature is enabled. It should be enabled by default.
Verify that the content that you want already exists in the remote repository. You cannot edit content in the main account. All of the content is fully synchronized with the remote repository.
Note
Any content that exists in the main account, but not on the remote repository, will be deleted
Define the repository.
Navigate to
→ → .Click the On/Off slider to enable the remote repositories.
The main account is automatically defined as the Production environment. This cannot be changed.
Enter the URL and connection credentials to the repository. Only SSH connections are supported.
Note
If you are using a passphrase, only RSA private keys are supported.
If your SSH connection uses a port other than port 22 (the default SSH port), you must include the ssh string and port number in the URL. In the following example, we use port 20017:
ssh://git@content.demisto.com:20017/~/my-project.git
Select the active branch from which you pull content.
Click Save.
In the Discard server changes screen, you are presented with content that exists in your production environment, but does not exist on the remote repository. This includes integrations, and their instances and classifiers.
Type
Discard
in the relevant field and click Continue. All of the content that appears in this screen is discarded and permanently deleted.Content from the remote repository is installed. This can take several minutes depending on the amount of content in the remote repository and your hardware configuration. In addition, your custom content is automatically backed up to the Cortex XSOAR server any time you change one of the remote repository settings. The backup is located under
/var/lib/demisto/backups/content-backup-*.tar.gz.
Pull Content from the Remote Repository
After you push content from the Development machine to the remote repository, it is available as an update for the main account.
Check for updates.
Click Install Content.