- NAME
-
- gcloud alpha scc manage custom-modules etd delete - delete an Event Threat Detection custom module
- SYNOPSIS
-
-
gcloud alpha scc manage custom-modules etd delete
MODULE_ID_OR_NAME
[--validate-only
] [--folder
=FOLDER_ID
|--organization
=ORGANIZATION_ID
|--parent
=PARENT
|--project
=PROJECT_ID_OR_NUMBER
] [GCLOUD_WIDE_FLAG …
]
-
- DESCRIPTION
-
(ALPHA)
Delete a Event Threat Detection custom module. User specifies the custom module as well as the parent of the module to delete. A validation_only flag is optional. When set to true only validations (including IAM checks) will done for the request (module will not be deleted). - EXAMPLES
-
To delete an Event Threat Detection custom module with ID
123456
for organization123
, run:gcloud alpha scc manage custom-modules etd delete 123456 --organization=123
To delete a Event Threat Detection custom module with ID
123456
for folder456
, run:gcloud alpha scc manage custom-modules etd delete 123456 --folder=456
To delete a Event Threat Detection custom module with ID
123456
for project789
, run:gcloud alpha scc manage custom-modules etd delete 123456 --project=789
You can also specify the parent more generally:
gcloud alpha scc manage custom-modules etd delete 123456 --parent=organizations/123
Or just specify the fully qualified module name:
gcloud alpha scc manage custom-modules etd delete organizations/123/locations/global/eventThreatDetectionCustomModules/123456
- POSITIONAL ARGUMENTS
-
MODULE_ID_OR_NAME
- The custom module ID or name. The expected format is {parent}/[locations/global]/eventThreatDetectionCustomModules/{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}.
- 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 etd delete
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-02-21 UTC.