mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Thu Feb 22 10:25:44 UTC 2024
This commit is contained in:
parent
5bf6fb3fc0
commit
8778dcbd7e
245 changed files with 9946 additions and 513 deletions
71
gcloud/scc/manage/custom-modules/etd/update
Normal file
71
gcloud/scc/manage/custom-modules/etd/update
Normal file
|
|
@ -0,0 +1,71 @@
|
|||
NAME
|
||||
gcloud scc manage custom-modules etd update - update an Event Threat
|
||||
Detection custom module
|
||||
|
||||
SYNOPSIS
|
||||
gcloud scc manage custom-modules etd update MODULE_ID_OR_NAME
|
||||
(--custom-config-file=CUSTOM_CONFIG_FILE
|
||||
--enablement-state=ENABLEMENT_STATE) [--validate-only]
|
||||
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --parent=PARENT
|
||||
| --project=PROJECT_ID_OR_NUMBER] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
EXAMPLES
|
||||
To update an Event Threat Detection custom module with ID 123456 for
|
||||
organization 123, run:
|
||||
|
||||
$ gcloud scc manage custom-modules etd update 123456 \
|
||||
--organization=organizations/123 --enablement-state="ENABLED" \
|
||||
--custom-config-file=custom_config.json
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
MODULE_ID_OR_NAME
|
||||
The custom module ID or name. The expected format is
|
||||
{parent}/[locations/global]/eventThreatDetectionCustomModules/{module_id}
|
||||
or just {module_id}. Where module_id is a numeric identifier 1-20
|
||||
characters in length. Parent is of the form organizations/{id},
|
||||
projects/{id or name}, folders/{id}.
|
||||
|
||||
REQUIRED FLAGS
|
||||
At least one of these must be specified:
|
||||
|
||||
--custom-config-file=CUSTOM_CONFIG_FILE
|
||||
Path to a JSON file that contains the custom config to set for the
|
||||
module.
|
||||
|
||||
--enablement-state=ENABLEMENT_STATE
|
||||
Sets the enablement state of the Event Threat Detection custom
|
||||
module. Valid options are ENABLED, DISABLED, OR INHERITED.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--validate-only
|
||||
If present, the request is validated (including IAM checks) but no
|
||||
action is taken.
|
||||
|
||||
At most one of these can 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 etd update
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue