Configure a Remote Repository on a Development Machine
contentrepository dev-prod dev prod remote repository repo Follow these instructions to configure a remote repository on a development machine.
To work with the remote repositories, you must have at least two machines, one for development and one for your production machine.
Before configuring the remote repository, review the following list of prerequisites:
- Ensure that you have network connectivity from the Cortex XSOAR server to your repository. All communication goes through the Cortex XSOAR server so it must have access to the remote repository.You cannot configure a Cortex XSOAR engine to manage communication to the remote repository.
- When creating a repository in your remote Git platform, verify that the repository contains branches. Defining the repository in Cortex XSOAR does not create the branches.
- Before toggling the remote repository feature on or off, or changing your repository configuration, ensure to back up your existing content to your local computer by navigating toand clickingSettingsAboutTroubleshootingCustom ContentExport.
- Configure the environment.
- On the machine that is designated to be the development environment, navigate toand clickSettingsAboutTroubleshootingCustom ContentImport.
- Verify that the content in both the development and production environments is synchronized before you proceed. If you do not synchronize the content, you might lose content in one of the environments.
- Define the Repository.
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. 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..
- Go to.SettingsAdvancedContent Repository
- Click the On/Off slider to enable the remote repositories
- Set the current machine as the development environment.
- 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://firstname.lastname@example.org:20017/~/my-project.git
- Select the active branch on which you will be working.
- In the Migrate server changes screen, determine whether or not you want to keep the content that is currently on the development server, or discard the changes and synchronize completely with the remote repository.Selected content: the current content on your server will be maintained and presented in the Local Changes window.Cleared content: the current content on the server will be overwritten by the content in the remote repository, if it exists.
- Manage Classifiers.
Each integration instance has its own classification. You can only push one classification per integration. When switching the remote repository to dev mode, if you have multiple instances of the same integration, the last classification that was saved appears in the Local Changes. You should decide which classification you want to keep, and make a small change to that classification
- Go to.SettingsIntegrationsClassification and Mapping
- Select the classifier that you want to keep.
- Make a small change and save the classifier.
- Push Content to the Remote Repository.
- Go to.SettingsLocal Changes
- Select the changes that you want to push to the remote repository, and clickPush.You should not manually push content to the remote repository. Use only the procedures outlined in the documentation to ensure that your content is properly updated in the production environment.
Recommended For You
Recommended videos not found.