gcloud scc manage custom-modules sha simulate

NAME: gcloud scc manage custom-modules sha simulate - command to simulate a SHA custom module
SYNOPSIS: gcloud scc manage custom-modules sha simulate --custom-config-from-file = CUSTOM_CONFIG --resource-from-file = TEST_DATA ( --folder = FOLDER_ID | --organization = ORGANIZATION_ID | --parent = PARENT | --project = PROJECT_ID_OR_NUMBER ) [ GCLOUD_WIDE_FLAG … ]
EXAMPLES: To simulate a Security Health Analytics custom module with ID 123456 for organization 123 , run:
gcloud scc manage custom-modules sha simulate 123456 --organization = 123 --custom-config-from-file = custom_config.yaml --resource-from-file = test.yaml

To simulate a Security Health Analytics custom module with ID 123456 for folder 456 , run:

gcloud scc manage custom-modules sha simulate 123456 --folder = 456 --custom-config-from-file = custom_config.yaml --resource-from-file = test.yaml

To simulate a Security Health Analytics custom module with ID 123456 for project 789 , run:

gcloud scc manage custom-modules sha simulate 123456 --project = 789 --custom-config-from-file = custom_config.yaml --resource-from-file = test.yaml

You can also specify the parent more generally:

gcloud scc manage custom-modules sha simulate 123456 --parent = organizations/123 --custom-config-from-file = custom_config.yaml --resource-from-file = test.yaml

Or just specify the fully qualified module name:

gcloud scc manage custom-modules sha simulate organizations/123/locations/global/effectiveSecurityHealthAnalyticsCustomModules/123456 --custom-config-from-file = custom_config.yaml --resource-from-file = test.yaml
REQUIRED FLAGS: --custom-config-from-file = CUSTOM_CONFIG

Path to a YAML custom configuration file. Use a full or relative path to a local file containing the value of custom_config.

--resource-from-file = TEST_DATA

Path to a YAML file that contains the resource data to validate the Security Health Analytics custom module against. Use a full or relative path to a local file containing the value of resource.

Exactly one of these must be specified:

--folder = FOLDER_ID

Folder associated with the custom module.

--organization = ORGANIZATION_ID

Organization associated with the custom module.

--parent = PARENT

Parent associated with the custom module. Can be one of organizations/<id>, projects/<id or name>, folders/<id>

--project = PROJECT_ID_OR_NUMBER

Project associated with the custom module.
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.
NOTES: This variant is also available:
gcloud alpha scc manage custom-modules sha simulate

gcloud scc manage custom-modules sha simulate Stay organized with collections Save and categorize content based on your preferences.

gcloud scc manage custom-modules sha simulate