- NAME
-
- gcloud alpha scc custom-modules sha update - update a Security Health Analytics custom module
- SYNOPSIS
-
-
gcloud alpha scc custom-modules sha update
CUSTOM_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 a Security Health Analytics custom module. - EXAMPLES
-
To update a Security Health Analytics custom module with ID
123456
for organization123, run
:gcloud alpha scc custom-modules sha update 123456 --organization=organizations/123 --enablement-state="ENABLED" --custom-config-from-file=custom_config.yaml
To update a Security Health Analytics custom module with ID
123456
for folder456
, run:gcloud alpha scc custom-modules sha update 123456 --folder=folders/456 --enablement-state="ENABLED" --custom-config-from-file=custom_config.yaml
To update a Security Health Analytics custom module with ID
123456
for project789
, run:gcloud alpha scc custom-modules sha update 123456 --project=projects/789 --enablement-state="ENABLED" --custom-config-from-file=custom_config.yaml
- POSITIONAL ARGUMENTS
-
CUSTOM_MODULE
- ID or the full resource name of the Security Health Analytics custom module. If you specify the full resource name, you do not need to specify the --organization, --folder, or --project flags.
- 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.
--enablement-state
=ENABLEMENT_STATE
-
Sets the enablement state of the Security Health Analytics custom module. From
the following list of possible enablement states, specify either enabled,
disabled or inherited only.
ENABLEMENT_STATE
must be one of:disabled
,enabled
,enablement-state-unspecified
,inherited
. --update-mask
=UPDATE_MASK
- Optional: If left unspecified (default), an update-mask is automatically created using 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 Security Health Analytics custom module resides. Formatted as
folders/456
or just456
. --organization
=ORGANIZATION
-
Organization where the Security Health Analytics custom module resides.
Formatted as
organizations/123
or just123
. --project
=PROJECT
-
ID or number of the project where the Security Health Analytics custom module
resides. Formatted as
projects/789
or 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 help
for details. - API REFERENCE
-
This command uses the
securitycenter/v1
API. The full documentation for 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 this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation-only early access
allowlist. This variant is also available:
gcloud scc custom-modules sha update
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-07-30 UTC.