Struct TransferJobArgs

pub struct TransferJobArgs {
    pub description: Output<String>,
    pub event_stream: Output<Option<TransferJobEventStream>>,
    pub name: Output<Option<String>>,
    pub notification_config: Output<Option<TransferJobNotificationConfig>>,
    pub project: Output<Option<String>>,
    pub schedule: Output<Option<TransferJobSchedule>>,
    pub status: Output<Option<String>>,
    pub transfer_spec: Output<TransferJobTransferSpec>,
}

Fields

description: Output<String>

Unique description to identify the Transfer Job.

event_stream: Output<Option<TransferJobEventStream>>

Specifies the Event-driven transfer options. Event-driven transfers listen to an event stream to transfer updated files. Structure documented below Either event_stream or schedule must be set.

name: Output<Option<String>>

The name of the Transfer Job. This name must start with “transferJobs/” prefix and end with a letter or a number, and should be no more than 128 characters ( transferJobs/^(?!OPI)[A-Za-z0-9-._~]*[A-Za-z0-9]$ ). For transfers involving PosixFilesystem, this name must start with transferJobs/OPI specifically ( transferJobs/OPI^[A-Za-z0-9-._~]*[A-Za-z0-9]$ ). For all other transfer types, this name must not start with transferJobs/OPI. Default the provider will assign a random unique name with transferJobs/{{name}} format, where name is a numeric value.

notification_config: Output<Option<TransferJobNotificationConfig>>

Notification configuration. This is not supported for transfers involving PosixFilesystem. Structure documented below.

project: Output<Option<String>>

The project in which the resource belongs. If it is not provided, the provider project is used.

schedule: Output<Option<TransferJobSchedule>>

Schedule specification defining when the Transfer Job should be scheduled to start, end and what time to run. Structure documented below. Either schedule or event_stream must be set.

status: Output<Option<String>>

Status of the job. Default: ENABLED. 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_spec: Output<TransferJobTransferSpec>

Transfer specification. Structure documented below.

---

Implementations

impl TransferJobArgs

pub fn builder() -> TransferJobArgsBuilder

Create an instance of TransferJobArgs using the builder syntax

Trait Implementations

impl Clone for TransferJobArgs

fn clone(&self) -> TransferJobArgs

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.