gcloud alpha scc manage custom-modules sha simulate Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud alpha scc manage custom-modules sha simulate - command to simulate a SHA custom module
- SYNOPSIS
gcloud alpha 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
123456for organization123, run:gcloudalphasccmanagecustom-modulesshasimulate123456--organization=123--custom-config-from-file=custom_config.yaml--resource-from-file=test.yamlTo simulate a Security Health Analytics custom module with ID
123456for folder456, run:gcloudalphasccmanagecustom-modulesshasimulate123456--folder=456--custom-config-from-file=custom_config.yaml--resource-from-file=test.yamlTo simulate a Security Health Analytics custom module with ID
123456for project789, run:gcloudalphasccmanagecustom-modulesshasimulate123456--project=789--custom-config-from-file=custom_config.yaml--resource-from-file=test.yamlYou can also specify the parent more generally:
gcloudalphasccmanagecustom-modulesshasimulate123456--parent=organizations/123--custom-config-from-file=custom_config.yaml--resource-from-file=test.yamlOr just specify the fully qualified module name:
gcloudalphasccmanagecustom-modulesshasimulateorganizations/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 localfile containing the value of custom_config.
--resource-from-file=TEST_DATA- Path to a YAML file that contains the resource data to validate the SecurityHealth Analytics custom module against. Use a full or relative path to a localfile 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 oforganizations/<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 helpfor details. - 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. This variant is also available:
gcloudsccmanagecustom-modulesshasimulate
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.