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.
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
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 to the local changes.
Push Content to the Remote Repository.
. The content
that you can push is shown in 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 Packs that
you have installed from Marketplace.
: If you want
to have more granular control over the items in the Content Packs
that you push, add the
and set the value to
Pack Items - 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
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.
When working with remote repositories and upgrading
to v6.0 and above, you must make sure to push your classifiers and
mappers on the dev environment before upgrading the production environment.
In the dialog box add an optional message and click
Review the contents and click
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.