End-of-Life (EoL)

Configure a Remote Repository on the Production Machine

contentrepository dev-prod dev prod remote repository repo Follow these steps to configure a remote repository on a production machine.
To work with the remote repositories, you must have at least two machines, one for your development environment and the other for your production environment.
Prerequisites
Before configuring the remote repository, review the following list of prerequisites:
  • Ensure that the Selective Propagation feature is enabled (default).
  • Verify that the content that you want already exists in the remote repository. You cannot edit content in the production environment. All of the content is fully synchronized with the remote repository.
    Any content that exists in the production environment, but not on the remote repository, will be deleted
  1. Define the repository
    .
    1. Navigate to
      Settings
      Advanced
      Content Repository
      .
    2. Click the On/Off slider to enable the remote repositories.
    3. Define the machine as the production environment.
    4. Enter the URL and connection credentials (including the private key) to the repository. Only SSH connections are supported.
      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
    5. Select the active branch from which you pull content.
    6. 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.
    7. 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.
  2. Pull Content from the Remote Repository
    Once you push content from the Development machine to the remote repository, it is available as an update for the production environment.
    1. Check for updates.
    2. Click
      Install Content
      .

Recommended For You