.TH "GCLOUD_SCC_BQEXPORTS_DELETE" 1



.SH "NAME"
.HP
gcloud scc bqexports delete \- delete a Security Command Center BigQuery export



.SH "SYNOPSIS"
.HP
\f5gcloud scc bqexports delete\fR \fIBIG_QUERY_EXPORT\fR [\fB\-\-location\fR=\fILOCATION\fR;\ default="global"] [\fB\-\-folder\fR=\fIFOLDER\fR\ |\ \fB\-\-organization\fR=\fIORGANIZATION\fR\ |\ \fB\-\-project\fR=\fIPROJECT\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Delete a Security Command Center BigQuery export.

BigQuery exports that are created with Security Command Center API V2 and later
include a \f5location\fR attribute. If the \f5location\fR attribute is included
in the resource name of a BigQuery export, you must specify it when referencing
the export. For example, the following BigQuery export name has
\f5location=eu\fR:
\f5organizations/123/locations/eu/bigQueryExports/test\-bq\-export\fR.



.SH "EXAMPLES"

To delete a BigQuery export given organization \f5123\fR with id
\f5test\-bq\-export\fR, run:

.RS 2m
$ gcloud scc bqexports delete test\-bq\-export \-\-organization=123
.RE

To delete a BigQuery export given folder \f5456\fR with \f5id
test\-bq\-export\fR, run:

.RS 2m
$ gcloud scc bqexports delete test\-bq\-export \-\-folder=456
.RE

To delete a BigQuery export given project \f5789\fR with id
\f5test\-bq\-export\fR, run:

.RS 2m
$ gcloud scc bqexports delete test\-bq\-export \-\-project=789
.RE

To delete the BigQuery export \f5test\-bq\-export\fR, with
\f5location=global\fR, from organization \f5123\fR, run:

.RS 2m
$ gcloud scc bqexports delete test\-bq\-export \-\-organization=123 \e
    \-\-location=global
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIBIG_QUERY_EXPORT\fR

ID of the BigQuery export e.g. \f5my\-bq\-export\fR or the full resource name of
the BigQuery export e.g. \f5organizations/123/bigQueryExports/my\-bq\-export\fR.


.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-location\fR=\fILOCATION\fR; default="global"

When data residency controls are enabled, this attribute specifies the location
in which the resource is located and applicable. The \f5location\fR attribute
can be provided as part of the fully specified resource name or with the
\f5\-\-location\fR argument on the command line. The default location is
\f5global\fR.

NOTE: If you override the endpoint to a regional endpoint
(https://cloud.google.com/security\-command\-center/docs/reference/rest/index.html?rep_location=global#regional\-service\-endpoint)
you must specify the correct data location
(https://cloud.google.com/security\-command\-center/docs/data\-residency\-support#locations)
using this flag. The default location on this command is unrelated to the
default location that is specified when data residency controls are enabled for
Security Command Center.

NOTE: If no location is specified, the default location is \f5global\fR AND the
request will be routed to the SCC V1 API. To use the SCC V2 API \- please
explicitly specify the flag.

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-folder\fR=\fIFOLDER\fR

Folder where the BigQuery export resides. Formatted as folders/456 or just 456.

.TP 2m
\fB\-\-organization\fR=\fIORGANIZATION\fR

Organization where the BigQuery export resides. Formatted as organizations/123
or just 123.

.TP 2m
\fB\-\-project\fR=\fIPROJECT\fR

Project (id or number) where the BigQuery export resides. Formatted as
projects/789 or just 789.


.RE
.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "API REFERENCE"

This command uses the Security Command Center API. For more information, see
Security Command Center API.
(https://cloud.google.com/security\-command\-center/docs/reference/rest)