Before contributing, please review the general contribution guidelines.
There are two ways to contribute an integration:
The mp tool helps automate the process of pulling, validating, and structuring your integration.
-
mp login --api-root <soar_url> --api-key <api_key> mp pull integration <integration_name> [option] --dest <pull_destionation_folder>
-
- Move the integration to the correct directory:
- For community integrations:
content/response_integration/third_party/community/ - For partner integrations:
content/response_integration/third_party/partner/
- For community integrations:
- Move the integration to the correct directory:
-
- Run
mp validateto ensure the integration passes all checks.
- Run
-
- Create a Pull Request on the
content-hubGitHub repository.
- Create a Pull Request on the
-
- The Content Hub team will review your submission and may request changes before merging.
If you prefer to contribute manually, follow these steps:
-
- In your Google SecOps instance, navigate to the integration and export it.
-
- At the root of the repository, run the following command:
Replace
mp build -i <integration_name> --deconstruct --src <path to exported integration>
<integration_name>with your integration's name.
- At the root of the repository, run the following command:
-
- Move the integration to the correct directory:
- For community integrations:
content/response_integration/third_party/community/ - For partner integrations:
content/response_integration/third_party/partner/
- For community integrations:
- Move the integration to the correct directory:
-
- Run
mp validateto ensure the integration passes all checks.
- Run
-
- Commit your changes and push them to your fork.
- Open a pull request against the main
content-hubrepository.
-
- The Content Hub team will review your submission and may request changes before merging.