gcloud alpha scc custom-modules sha test

NAME
gcloud alpha scc custom-modules sha test - test a Security Health Analytics custom module
SYNOPSIS
gcloud alpha scc custom-modules sha testCUSTOM_MODULE--test-data-from-file=PATH_TO_FILE[--custom-config-from-file=PATH_TO_FILE][--display-name=DISPLAY_NAME][--folder=FOLDER    |--organization=ORGANIZATION    |--project=PROJECT][GCLOUD_WIDE_FLAG]
DESCRIPTION
(ALPHA) Test a Security Health Analytics custom module.
EXAMPLES
To test a Security Health Analytics custom module with ID123456for organization123, run:
gcloudalphascccustom-modulesshatest123456--organization=organizations/123--display-name="test_display_name"--custom-config-from-file=/tmp/custom_config.yaml--test-data-from-file=/tmp/test_data.yaml

To test a Security Health Analytics custom module with ID123456for folder456, run:

gcloudalphascccustom-modulesshatest123456--folder=folders/456--display-name="test_display_name"--custom-config-from-file=/tmp/custom_config.yaml--test-data-from-file=/tmp/test_data.yaml

To test a Security Health Analytics custom module with ID123456for project789, run:

gcloudalphascccustom-modulesshatest123456--project=projects/789--display-name="test_display_name"--custom-config-from-file=/tmp/custom_config.yaml--test-data-from-file=/tmp/test_data.yaml
POSITIONAL ARGUMENTS
CUSTOM_MODULE
ID or the full resource name of the Security Health Analytics custom module. Ifyou specify the full resource name, you do not need to specify the--organization, --folder, or --project flags.
REQUIRED FLAGS
--test-data-from-file=PATH_TO_FILE
Path to a YAML file that contains the resource data to test the Security HealthAnalytics custom module against. Use a full or relative path to a local filecontaining the value of test_data.
OPTIONAL FLAGS
--custom-config-from-file=PATH_TO_FILE
Path to a YAML file that contains the configuration for the Security HealthAnalytics custom module. If not specified, the existing module with the given IDor resource name is used. Use a full or relative path to a local file containingthe value of custom_config.
--display-name=DISPLAY_NAME
Sets the display name of the Security Health Analytics custom module. Thisdisplay name becomes the finding category for all findings that are returned bythis the custom module. The display name must be between 1 and 128 characters,start with a lowercase letter, and contain alphanumeric characters orunderscores only. Only relevant when--custom-config-from-file isalso specified.
At most one of these can be specified:
--folder=FOLDER
Folder where the Security Health Analytics custom module resides. Formatted asfolders/456 or just456.
--organization=ORGANIZATION
Organization where the Security Health Analytics custom module resides.Formatted asorganizations/123 or just123.
--project=PROJECT
ID or number of the project where the Security Health Analytics custom moduleresides. Formatted asprojects/789 or just789.
GCLOUD WIDE FLAGS
These flags are available to all commands:--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.

Run$gcloud help for details.

API REFERENCE
This command uses thesecuritycenter/v1 API. The full documentationfor this API can be found at:https://cloud.google.com/security-command-center
NOTES
This command is currently in alpha and might change without notice. If thiscommand fails with API permission errors despite specifying the correct project,you might be trying to access an API with an invitation-only early accessallowlist.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-05-07 UTC.