gcloud: Thu Feb 22 10:25:44 UTC 2024

gcloud/alpha/scc/manage/custom-modules/sha/update

@@ -0,0 +1,74 @@
+NAME
+    gcloud alpha scc manage custom-modules sha update - update a Security
+        Health Analytics custom module
+
+SYNOPSIS
+    gcloud alpha scc manage custom-modules sha 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 Security Health Analytics custom module with ID 123456 for
+    organization 123, run:
+
+        $ gcloud alpha scc manage custom-modules sha update 123456 \
+          --organization=organizations/123 --enablement-state="ENABLED" \
+          --custom-config-file=custom_config.yaml
+
+POSITIONAL ARGUMENTS
+     MODULE_ID_OR_NAME
+        The custom module ID or name. The expected format is
+        {parent}/[locations/global]/securityHealthAnalyticsCustomModules/{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 YAML file that contains the custom config to set for the
+          module.
+
+       --enablement-state=ENABLEMENT_STATE
+          Sets the enablement state of the Security Health Analytics 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 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 manage custom-modules sha update
+