gcloud alpha fault-testing exclusion-windows delete

NAME
gcloud alpha fault-testing exclusion-windows delete - delete exclusionWindows
SYNOPSIS
gcloud alpha fault-testing exclusion-windows delete (EXCLUSION_WINDOW : --location=LOCATION) [GCLOUD_WIDE_FLAG]
DESCRIPTION
(ALPHA) Delete an exclusionWindow
EXAMPLES
To delete the exclusionWindow, run:
gcloud alpha fault-testing exclusion-windows delete
POSITIONAL ARGUMENTS
ExclusionWindow resource - The name of the exclusion window to delete. Format: projects/{project}/locations/{location}/exclusionWindows/{exclusion_window}. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways.

To set the project attribute:

  • provide the argument exclusion_window on the command line with a fully specified name;
  • provide the argument --project on the command line;
  • set the property core/project.

This must be specified.

EXCLUSION_WINDOW
ID of the exclusionWindow or fully qualified identifier for the exclusionWindow.

To set the exclusion_window attribute:

  • provide the argument exclusion_window on the command line.

This positional argument must be specified if any of the other arguments in this group are specified.

--location=LOCATION
The location id of the exclusionWindow resource.

To set the location attribute:

  • provide the argument exclusion_window on the command line with a fully specified name;
  • provide the argument --location on the command line.
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 faulttesting/v1alpha API. The full documentation for this API can be found at: https://docs.cloud.google.com/fault-injection-testing
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.