.TH "GCLOUD_SCC_CUSTOM\-MODULES_SHA_UPDATE" 1



.SH "NAME"
.HP
gcloud scc custom\-modules sha update \- update a Security Health Analytics custom module



.SH "SYNOPSIS"
.HP
\f5gcloud scc custom\-modules sha update\fR \fICUSTOM_MODULE\fR [\fB\-\-custom\-config\-from\-file\fR=\fIPATH_TO_FILE\fR] [\fB\-\-enablement\-state\fR=\fIENABLEMENT_STATE\fR] [\fB\-\-update\-mask\fR=\fIUPDATE_MASK\fR] [\fB\-\-folder\fR=\fIFOLDER\fR\ |\ \fB\-\-organization\fR=\fIORGANIZATION\fR\ |\ \fB\-\-project\fR=\fIPROJECT\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Update a Security Health Analytics custom module.



.SH "EXAMPLES"

To update a Security Health Analytics custom module with ID \f5123456\fR for
organization \f5123, run\fR:

.RS 2m
$ gcloud scc custom\-modules sha update 123456 \e
    \-\-organization=organizations/123 \-\-enablement\-state="ENABLED" \e
    \-\-custom\-config\-from\-file=custom_config.yaml
.RE

To update a Security Health Analytics custom module with ID \f5123456\fR for
folder \f5456\fR, run:

.RS 2m
$ gcloud scc custom\-modules sha update 123456 \-\-folder=folders/456 \e
    \-\-enablement\-state="ENABLED" \e
    \-\-custom\-config\-from\-file=custom_config.yaml
.RE

To update a Security Health Analytics custom module with ID \f5123456\fR for
project \f5789\fR, run:

.RS 2m
$ gcloud scc custom\-modules sha update 123456 \e
    \-\-project=projects/789 \-\-enablement\-state="ENABLED" \e
    \-\-custom\-config\-from\-file=custom_config.yaml
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fICUSTOM_MODULE\fR

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.


.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-custom\-config\-from\-file\fR=\fIPATH_TO_FILE\fR

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.

.TP 2m
\fB\-\-enablement\-state\fR=\fIENABLEMENT_STATE\fR

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. \fIENABLEMENT_STATE\fR must be one of:
\fBdisabled\fR, \fBenabled\fR, \fBenablement\-state\-unspecified\fR,
\fBinherited\fR.

.TP 2m
\fB\-\-update\-mask\fR=\fIUPDATE_MASK\fR

Optional: If left unspecified (default), an update\-mask is automatically
created using the flags specified in the command and only those values are
updated.

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-folder\fR=\fIFOLDER\fR

Folder where the Security Health Analytics custom module resides. Formatted as
\f5folders/456\fR or just \f5456\fR.

.TP 2m
\fB\-\-organization\fR=\fIORGANIZATION\fR

Organization where the Security Health Analytics custom module resides.
Formatted as \f5organizations/123\fR or just \f5123\fR.

.TP 2m
\fB\-\-project\fR=\fIPROJECT\fR

ID or number of the project where the Security Health Analytics custom module
resides. Formatted as \f5projects/789\fR or just \f5789\fR.


.RE
.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "API REFERENCE"

This command uses the \fBsecuritycenter/v1\fR API. The full documentation for
this API can be found at: https://cloud.google.com/security\-command\-center



.SH "NOTES"

This variant is also available:

.RS 2m
$ gcloud alpha scc custom\-modules sha update
.RE