gcloud alpha scc custom-modules etd update Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud alpha scc custom-modules etd update - update an Event Threat Detection custom module
- SYNOPSIS
gcloud alpha scc custom-modules etd updateCUSTOM_MODULE[--custom-config-from-file=PATH_TO_FILE][--enablement-state=ENABLEMENT_STATE][--update-mask=UPDATE_MASK][--folder=FOLDER|--organization=ORGANIZATION|--project=PROJECT][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
(ALPHA)Update an Event Threat Detection custom module.- EXAMPLES
- To update an Event Threat Detection custom module with ID
123456for organization123, run:gcloudalphascccustom-modulesetdupdate123456--organization=organizations/123--enablement-state="ENABLED"--custom-config-from-file=custom_config.jsonTo update an Event Threat Detection custom module with ID
123456for folder456, run:gcloudalphascccustom-modulesetdupdate123456--folder=folders/456--enablement-state="ENABLED"--custom-config-from-file=custom_config.jsonTo update an Event Threat Detection custom module with ID
123456for project789, run:gcloudalphascccustom-modulesetdupdate123456--project=projects/789--enablement-state="ENABLED"--custom-config-from-file=custom_config.json - POSITIONAL ARGUMENTS
CUSTOM_MODULE- ID or the full resource name of the Event Threat Detection custom module. If youspecify the full resource name, you do not need to specify the
--organization,--folder, or--projectflags.
- FLAGS
--custom-config-from-file=PATH_TO_FILE- Path to a JSON file that contains the configuration for the Event ThreatDetection custom module. Use a full or relative path to a local file containingthe value of custom_config.
--enablement-state=ENABLEMENT_STATE- Sets the enablement state of the Event Threat Detection custom module. Validoptions are
ENABLED,DISABLED, andINHERITED.ENABLEMENT_STATEmust be one of:disabled,enabled,enablement-state-unspecified,inherited. --update-mask=UPDATE_MASK- Optional: If left unspecified (default), an update mask is automatically createdusing the flags specified in the command and only those values are updated.
- At most one of these can be specified:
--folder=FOLDER- Folder where the Event Threat Detection custom module resides. Formatted as
folders/456or just456. --organization=ORGANIZATION- Organization where the Event Threat Detection custom module resides. Formattedas
organizations/123or just123. --project=PROJECT- ID or number of the project where the Event Threat Detection custom moduleresides. 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 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.