gcloud scc custom-modules sha simulate
Stay organized with collections
Save and categorize content based on your preferences.
- NAME
-
- gcloud scc custom-modules sha simulate - validates a Security Health Analytics custom module
- SYNOPSIS
-
-
gcloud scc custom-modules sha simulate--custom-config-from-file=PATH_TO_FILE--resource-from-file=PATH_TO_FILE(--folder=FOLDER|--organization=ORGANIZATION|--project=PROJECT) [GCLOUD_WIDE_FLAG …]
-
- DESCRIPTION
- Validates a given Security Health Analytics custom module and resource.
- EXAMPLES
-
To validate a Security Health Analytics custom module against a custom resource
for organization
123, run:gcloudscccustom-modulesshasimulate--organization=organizations/123--custom-config-from-file=/tmp/custom_config.yaml--resource-from-file=/tmp/resource.yamlTo validate a Security Health Analytics custom module against a custom resource for folder
456, run:gcloudscccustom-modulesshasimulate--folder=folders/456--custom-config-from-file=/tmp/custom_config.yaml--resource-from-file=/tmp/resource.yamlTo validate a Security Health Analytics custom module against a custom resource for project
789, run:gcloudscccustom-modulesshasimulate--project=projects/789--custom-config-from-file=/tmp/custom_config.yaml--resource-from-file=/tmp/resource.yaml - REQUIRED FLAGS
-
--custom-config-from-file=PATH_TO_FILE- Path to a YAML file that contains the configuration for the Security Health Analytics custom module. Use a full or relative path to a local file containing the value of custom_config.
--resource-from-file=PATH_TO_FILE- 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-
Folder that will own the Security Health Analytics custom module. Formatted as
folders/456or just456. --organization=ORGANIZATION-
Organization that will own the Security Health Analytics custom module.
Formatted as
organizations/123or just123. --project=PROJECT-
ID or number of the project that will own the Security Health Analytics custom
module. Formatted as
projects/789or 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 helpfor details. - API REFERENCE
-
This command uses the
securitycenter/v1API. The full documentation for this API can be found at: https://cloud.google.com/security-command-center - NOTES
-
This variant is also available:
gcloudalphascccustom-modulesshasimulate