Validate content (integrations and playbooks) within the Content Hub.
mp validate [SUBCOMMAND] [OPTIONS]Validate specific response integrations.
Usage:
mp validate integration [INTEGRATIONS]... [OPTIONS]Arguments:
INTEGRATIONS: A list of integrations to validate.
Options:
| Option | Shorthand | Description | Type | Default |
|---|---|---|---|---|
--quiet |
-q |
Suppress most logging output during runtime. | bool |
False |
--verbose |
-v |
Enable verbose logging output during runtime. | bool |
False |
Validate specific playbooks.
Usage:
mp validate playbook [PLAYBOOKS]... [OPTIONS]Arguments:
PLAYBOOKS: A list of playbooks to validate.
Options:
| Option | Shorthand | Description | Type | Default |
|---|---|---|---|---|
--quiet |
-q |
Suppress most logging output during runtime. | bool |
False |
--verbose |
-v |
Enable verbose logging output during runtime. | bool |
False |
Validate entire content repositories.
Usage:
mp validate repository [REPOSITORIES]... [OPTIONS]Arguments:
REPOSITORIES: One or more repository types to validate. Options:google: Commercial integrations.third_party: Community and partner integrations.playbooks: Playbooks.
Options:
| Option | Shorthand | Description | Type | Default |
|---|---|---|---|---|
--quiet |
-q |
Suppress most logging output during runtime. | bool |
False |
--verbose |
-v |
Enable verbose logging output during runtime. | bool |
False |
mp validate integration my_integrationmp validate playbook my_playbookmp validate repository third_partyThe following flag-based usage is deprecated and will be removed in future versions. Please use the subcommands above.
mp validate --integration <name>
mp validate --playbook <name>
mp validate --repository <type>