API Reference google_api_data_pipelines v0.3.0

Modules

API client metadata for GoogleApi.DataPipelines.V1.

API calls for all endpoints tagged Projects.

Handle Tesla connections for GoogleApi.DataPipelines.V1.

Pipeline job details specific to the Dataflow API. This is encapsulated here to allow for more executors to store their specific details separately.

The environment values to be set at runtime for a Flex Template.

Definition of the job information maintained by the pipeline. Fields in this entity are retrieved from the executor API (e.g. Dataflow API).

A request to launch a Dataflow job from a Flex Template.

Parameters to provide to the template being launched.

The main pipeline entity and all the necessary metadata for launching and managing linked jobs.

Details of the schedule the pipeline runs on.

The version of the SDK used to run the job.

Workload details for creating the pipeline jobs.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for Empty is empty JSON object {}.

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.