StorageTransfer
import { StorageTransfer } from "https://googleapis.deno.dev/v1/storagetransfer:v1.ts";
Transfers data from external data sources to a Google Cloud Storage bucket or between Google Cloud Storage buckets.
§Methods
Returns the Google service account that is used by Storage Transfer Service to access buckets in the project where transfers run or in other projects. Each Google service account is associated with one Google Cloud project. Users should add this service account to the Google Cloud Storage bucket ACLs to grant access to Storage Transfer Service. This service account is created and owned by Storage Transfer Service and can only be used by Storage Transfer Service.
Required. The ID of the Google Cloud project that the Google service account is associated with.
Creates an agent pool resource.
Required. The ID of the Google Cloud project that owns the agent pool.
Lists agent pools.
Required. The ID of the Google Cloud project that owns the job.
Updates an existing agent pool resource.
Required. Specifies a unique string that identifies the agent pool. Format: projects/{project_id}/agentPools/{agent_pool_id}
Creates a transfer job that runs periodically.
Deletes a transfer job. Deleting a transfer job sets its status to DELETED.
Required. The job to delete.
Lists transfer jobs.
Updates a transfer job. Updating a job's transfer spec does not affect transfer operations that are running already. Note: The job's status field can be modified using this RPC (for example, to set a job's status to DELETED, DISABLED, or ENABLED).
Required. The name of job to update.
Starts a new operation for the specified transfer job. A TransferJob
has
a maximum of one active TransferOperation
. If this method is called while
a TransferOperation
is active, an error is returned.
Required. The name of the transfer job.
Cancels a transfer. Use the transferOperations.get method to check if the
cancellation succeeded or if the operation completed despite the cancel
request. When you cancel an operation, the currently running transfer is
interrupted. For recurring transfer jobs, the next instance of the transfer
job will still run. For example, if your job is configured to run every day
at 1pm and you cancel Monday's operation at 1:05pm, Monday's transfer will
stop. However, a transfer job will still be attempted on Tuesday. This
applies only to currently running operations. If an operation is not
currently running, cancel
does nothing. Caution: Canceling a transfer
job can leave your data in an unknown state. We recommend that you restore
the state at both the destination and the source after the cancel
request
completes so that your data is in a consistent state. When you cancel a
job, the next job computes a delta of files and may repair any inconsistent
state. For instance, if you run a job every day, and today's job found 10
new files and transferred five files before you canceled the job,
tomorrow's transfer operation will compute a new delta with the five files
that were not copied today plus any new files discovered tomorrow.
The name of the operation resource to be cancelled.
Lists transfer operations. Operations are ordered by their creation time in reverse chronological order.
Required. The name of the type being listed; must be transferOperations
.