gcloud batch jobs delete

NAME

gcloud batch jobs delete - delete a job

SYNOPSIS

gcloud batch jobs delete (JOB : --location=LOCATION) [GCLOUD_WIDE_FLAG …]

DESCRIPTION

This command can fail for the following reasons:

• The job specified does not exist.
• The active account does not have permission to delete the given job.

EXAMPLES

To delete the job with name projects/foo/locations/us-central1/jobs/bar, run:

gcloud batch jobs delete projects/foo/locations/us-central1/jobs/bar

POSITIONAL ARGUMENTS

Job resource - The Batch job resource. If --location not specified,the current batch/location is used. 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 JOB 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.

JOB

ID of the job or fully qualified identifier for the job.

To set the job attribute:

• provide the argument JOB on the command line.

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

--location=LOCATION

Google Cloud location for the job.

To set the location attribute:

• provide the argument JOB on the command line with a fully specified name;
• provide the argument --location on the command line;
• set the property batch/location.

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

These variants are also available:

gcloud alpha batch jobs delete

gcloud beta batch jobs delete