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

gcloud/alpha/scc/manage/custom-modules/etd/create

@@ -0,0 +1,74 @@
+NAME
+    gcloud alpha scc manage custom-modules etd create - create an Event Threat
+        Detection custom module
+
+SYNOPSIS
+    gcloud alpha scc manage custom-modules etd create
+        --custom-config-file=CUSTOM_CONFIG --display-name=DISPLAY-NAME
+        --enablement-state=ENABLEMENT_STATE --module-type=MODULE_TYPE
+        (--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --parent=PARENT
+          | --project=PROJECT_ID_OR_NUMBER) [--validate-only]
+        [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    To create an Event Threat Detection custom module for organization 123,
+    run:
+
+        $ gcloud alpha scc manage custom-modules etd create \
+            --organization=organizations/123 \
+            --display-name="test_display_name" \
+            --module-type="CONFIGURABLE_BAD_IP" \
+            --enablement-state="ENABLED" --custom-config-file=config.json
+
+REQUIRED FLAGS
+     --custom-config-file=CUSTOM_CONFIG
+        Path to a JSON custom configuration file of the ETD custom module.
+
+     --display-name=DISPLAY-NAME
+        The display name of the custom module.
+
+     --enablement-state=ENABLEMENT_STATE
+        Sets the enablement state of the Event Threat Detection custom module.
+        Valid options are ENABLED, DISABLED, OR INHERITED.
+
+     --module-type=MODULE_TYPE
+        Type of the custom module. For a list of valid module types please
+        visit
+        https://cloud.google.com/security-command-center/docs/custom-modules-etd-overview#custom_modules_and_templates.
+
+     Exactly one of these must 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.
+
+OPTIONAL FLAGS
+     --validate-only
+        If present, the request is validated (including IAM checks) but no
+        action is taken.
+
+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 etd create
+