You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The XSOAR CI/CD deployment model uses two key components; the demisto-sdk and the ContentManagement Content Pack. For single instance environments, the process involves using the demisto-sdk to build custom content packs that are then uploaded to an Artifact Server and then installed via Playbooks from the ContentManagement Content Pack. This process doesn't work for Multitenant environments, as content needs to be installed on the Main Server which cannot execute Playbooks. In these cases, custom content packs need to be installed from the build server using the demisto-sdk upload subcommand. This will not automatically install dependencies from the marketplace. To install those, the MarketPlaceInstallerFromCICD build script needs to be executed using the xsoar_config.json produced by the demisto-sdk.
Problem
The MarketPlaceInstallerFromCICD is just a patched version of the MarketplacePackInstaller script. This automation is used within the ContentManagement playbook designed for the Artifact Server. It uses the demistomock.py, which as the name implies is just a mock library used to emulate the real demisto library imported into automations executed within a container on a demisto server. While the script might print results to stdout, it lacks the capabilities to make an HTTP request... let alone remotely execute the automations required to install content packs from the marketplace. At best, this script can produce a stdout of what it would do if it was executed on a demisto server.
Solution
This is not a viable solution and framing as such is misleading for users who cannot use the Artifact Server deployment model (e.g. anyone with a Multitenant environment). It's impossible for the script to work in its current state without significant refactoring. The script should be removed from this repo and the xsoar-ci-cd docs until a viable solution is available.
The text was updated successfully, but these errors were encountered:
Summary
The XSOAR CI/CD deployment model uses two key components; the demisto-sdk and the ContentManagement Content Pack. For single instance environments, the process involves using the demisto-sdk to build custom content packs that are then uploaded to an Artifact Server and then installed via Playbooks from the ContentManagement Content Pack. This process doesn't work for Multitenant environments, as content needs to be installed on the Main Server which cannot execute Playbooks. In these cases, custom content packs need to be installed from the build server using the demisto-sdk upload subcommand. This will not automatically install dependencies from the marketplace. To install those, the MarketPlaceInstallerFromCICD build script needs to be executed using the
xsoar_config.json
produced by the demisto-sdk.Problem
The MarketPlaceInstallerFromCICD is just a patched version of the MarketplacePackInstaller script. This automation is used within the ContentManagement playbook designed for the Artifact Server. It uses the demistomock.py, which as the name implies is just a mock library used to emulate the real demisto library imported into automations executed within a container on a demisto server. While the script might print results to stdout, it lacks the capabilities to make an HTTP request... let alone remotely execute the automations required to install content packs from the marketplace. At best, this script can produce a stdout of what it would do if it was executed on a demisto server.
Solution
This is not a viable solution and framing as such is misleading for users who cannot use the Artifact Server deployment model (e.g. anyone with a Multitenant environment). It's impossible for the script to work in its current state without significant refactoring. The script should be removed from this repo and the xsoar-ci-cd docs until a viable solution is available.
The text was updated successfully, but these errors were encountered: