17.11. Pipelines Details RPC¶
Requests details of a pipeline.
rpc Details (PipelinesDetailsRequest) returns (stream PipelinesDetailsResponse);
17.11.1. Messages¶
PipelinesDetailsRequest
PipelinesDetailsResponse
17.12. PipelinesDetailsRequest¶
message PipelinesDetailsRequest { RequestHeader header = 1; Identifier pipeline_id = 2; }
17.12.1. Properties¶
17.12.1.2. pipeline_id¶
type: message
Unique identifier of the pipeline.
Required. If the identifier value is omitted from the request or does not match any known pipeline identifier, Clara Deploy SDK will be unable to fulfill the request.
See Identifier for details.
17.13. PipelinesDetailsResponse¶
message PipelineDetailsResponse { ResponseHeader header = 1; Identifier pipeline_id = 2; string name = 3; PipelineDefinitionFile definition = 4; }
Clara Deploy SDK Pipelines service will respond to any details request with a PipelinesDetailsResponse message. Requestors can use the response message to determine the result of their request.
17.13.1. Properties¶
17.13.1.2. pipeline_id¶
type: message
Unique identifier of the pipeline.
See Identifier for details.
17.13.1.4. 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.
See PipelineDefinitionFile for details.