gcloud alpha scc custom-modules etd delete

NAME: gcloud alpha scc custom-modules etd delete - delete an Event Threat Detection custom module
SYNOPSIS: gcloud alpha scc custom-modules etd delete CUSTOM_MODULE [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG …]
DESCRIPTION: (ALPHA) Delete an Event Threat Detection custom module.
EXAMPLES: To delete an Event Threat Detection custom module with ID 123456 for organization 123, run:
gcloud alpha scc custom-modules etd delete 123456 --organization=organizations/123

To delete an Event Threat Detection custom module with ID 123456 for folder 456, run:
gcloud alpha scc custom-modules etd delete 123456 --folder=folders/456

To delete an Event Threat Detection custom module with ID 123456 for project 789, run:
gcloud alpha scc custom-modules etd delete 123456 --project=projects/789
POSITIONAL ARGUMENTS: CUSTOM_MODULE

ID or the full resource name of the Event Threat Detection custom module. If you specify the full resource name, you do not need to specify the --organization, --folder, or --project flags.
FLAGS: At most one of these can be specified:

--folder=FOLDER

Folder where the Event Threat Detection custom module resides. Formatted as folders/456 or just 456.

--organization=ORGANIZATION

Organization where the Event Threat Detection custom module resides. Formatted as organizations/123 or just 123.

--project=PROJECT

ID or number of the project where the Event Threat Detection custom module resides. Formatted as projects/789 or just 789.
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.