TransferJob
import type { TransferJob } from "https://googleapis.deno.dev/v1/storagetransfer:v1.ts";
This resource represents the configuration of a transfer job that runs periodically.
§Properties
A description provided by the user for the job. Its max length is 1024 bytes when Unicode-encoded.
Specifies the event stream for the transfer job for event-driven transfers. When EventStream is specified, the Schedule fields are ignored.
The name of the most recently started TransferOperation of this JobConfig. Present if a TransferOperation has been created for this JobConfig.
Logging configuration.
A unique name (within the transfer project) assigned when the job is
created. If this field is empty in a CreateTransferJobRequest, Storage
Transfer Service assigns a unique name. Otherwise, the specified name is
used as the unique name for this job. If the specified name is in use by a
job, the creation request fails with an ALREADY_EXISTS error. This name
must start with "transferJobs/"
prefix and end with a letter or a number,
and should be no more than 128 characters. For transfers involving
PosixFilesystem, this name must start with transferJobs/OPI
specifically.
For all other transfer types, this name must not start with
transferJobs/OPI
. Non-PosixFilesystem example:
"transferJobs/^(?!OPI)[A-Za-z0-9-._~]*[A-Za-z0-9]$"
PosixFilesystem
example: "transferJobs/OPI^[A-Za-z0-9-._~]*[A-Za-z0-9]$"
Applications
must not rely on the enforcement of naming requirements involving OPI.
Invalid job names fail with an INVALID_ARGUMENT error.
Notification configuration.
Replication specification.
Status of the job. This value MUST be specified for
CreateTransferJobRequests
. Note: The effect of the new job status
takes place during a subsequent job run. For example, if you change the job
status from ENABLED to DISABLED, and an operation spawned by the transfer
is running, the status change would not affect the current operation.
Transfer specification.