14.2. Pipelines Create RPC

Requests the creation of a new pipeline, based on a definition provided to the service.

rpc Create (stream PipelinesCreateRequest) returns (PipelinesCreateResponse)

14.2.1. Types

  • PipelinesCreateRequest

  • PipelinesCreateResponse


14.3. PipelinesCreateRequest

message PipelinesCreateRequest {
  RequestHeader header = 1;
  PipelineDefinitionFile definition = 2;
}

14.3.1. Properties

14.3.1.2. definition

type: message

A file in the definition of the pipeline.

Note that this request is streamed to allow large pipeline definitions beyond the limits of a single GRPC message size. In the case of large pipelines, parts of the pipeline definition may be chunked into multiple parts such that the server will concatenate all parts having the same name into a single file server-side.

Definitions spanning multiple files can also be streamed via the create request.

Pipeline definition file names are case-preserving. When a definition contains multiple files with names that only differ by case, they will be combined into a single file using one of the colliding names as the combined file’s name.

See PipelineDefinitionFile for details.


14.4. PipelinesCreateResponse

message PipelineCreateResponse {
 ResponseHeader header = 1;
 Identifier pipeline_id = 2;
}

Clara Deploy SDK Pipelines service will respond to any creation request with a PipelinesCreateResponse message. Requestors can use the response message to determine the result of their request.

14.4.1. Properties

14.4.1.1. header

type: message

Standard RPC response header.

See ResponseHeader for details.

14.4.1.2. pipeline_id

type: message

Unique identifier of the pipeline.

See Identifier for details.