Push content to a remote repository and control access
for pushing content. Cortex XSOAR dev-prod dev prod remote repository
Once you develop your content, for it to be
available as part of a content update for the production environment,
you must push the changes to the remote repository.
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
You can save versions and manage revisions
locally using the Save Version button. Alternatively, you can click
and save the changes.
options are only available for the following content types:
For all other content types, your changes
are automatically saved locally.
You can push individual
items such as a playbook, or Content Packs as a whole. If you want
to have more granular control over the items in the Content Packs
that you push, add the
configuration and set the value to
working with remote repositories and upgrading to v6.0 and above,
push your classifiers and mappers on the development environment before
upgrading the production environment.
Push content to the Remote Repository.
. Push the following
content according to the tabs:
: Content that is not related
specifically to a Content Pack. For example, customized automations or
If you have already pushed a Content Pack and later
edit one of its content items, the edited items will appear in the
: All of the content that is
specific to the Content Packs you installed from Marketplace.
Select the changes that you want to push to the remote
repository, and click
In the dialog box, add an optional message and click
If the items have dependencies, review the contents
Sometimes you may not want to push all content, Content
Pack dependencies, etc. For example, when a user makes a change
in a playbook that includes an automation dependency to which another
user is adding a feature, and the change does not require the new
feature (version) of the automation, you can push the playbook without
the new automation.
On the remote repository, install the new content.
At the top of any page, click
In the dialog box, click
You can also check for new content that has been pushed.
If conflicts appear, click
one of the following:
Keeps the local content in
your production environment.
: Deletes the local content
and installs the content from the remote repository.
to save the changes.
) If you want to control access when
pushing content, on the remote repository, do the following