Struct aws_sdk_proton::client::fluent_builders::UpdateServicePipeline

pub struct UpdateServicePipeline<C = DynConnector, M = DefaultMiddleware, R = Standard> { /* fields omitted */ }

Fluent builder constructing a request to UpdateServicePipeline.

Update the service pipeline.

There are four modes for updating a service pipeline as described in the following. The deploymentType field defines the mode.

NONE

In this mode, a deployment doesn't occur. Only the requested metadata parameters are updated.

CURRENT_VERSION

In this mode, the service pipeline is deployed and updated with the new spec that you provide. Only requested parameters are updated. Don’t include minor or major version parameters when you use this deployment-type.

MINOR_VERSION

In this mode, the service pipeline is deployed and updated with the published, recommended (latest) minor version of the current major version in use, by default. You can also specify a different minor version of the current major version in use.

MAJOR_VERSION

In this mode, the service pipeline is deployed and updated with the published, recommended (latest) major and minor version of the current template by default. You can also specify a different major version that is higher than the major version in use and a minor version (optional).

Implementations

impl<C, M, R> UpdateServicePipeline<C, M, R> where
    C: SmithyConnector,
    M: SmithyMiddleware<C>,
    R: NewRequestPolicy, 

pub async fn send(
    self
) -> Result<UpdateServicePipelineOutput, SdkError<UpdateServicePipelineError>> where
    R::Policy: SmithyRetryPolicy<UpdateServicePipelineInputOperationOutputAlias, UpdateServicePipelineOutput, UpdateServicePipelineError, UpdateServicePipelineInputOperationRetryAlias>, 

Sends the request and returns the response.

If an error occurs, an SdkError will be returned with additional details that can be matched against.

By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.

pub fn service_name(self, inp: impl Into<String>) -> Self

The name of the service to that the pipeline is associated with.

pub fn set_service_name(self, input: Option<String>) -> Self

The name of the service to that the pipeline is associated with.

pub fn spec(self, inp: impl Into<String>) -> Self

The spec for the service pipeline to update.

pub fn set_spec(self, input: Option<String>) -> Self

The spec for the service pipeline to update.

pub fn deployment_type(self, inp: DeploymentUpdateType) -> Self

The deployment type.

There are four modes for updating a service pipeline as described in the following. The deploymentType field defines the mode.

NONE

In this mode, a deployment doesn't occur. Only the requested metadata parameters are updated.

CURRENT_VERSION

In this mode, the service pipeline is deployed and updated with the new spec that you provide. Only requested parameters are updated. Don’t include minor or major version parameters when you use this deployment-type.

MINOR_VERSION

In this mode, the service pipeline is deployed and updated with the published, recommended (latest) minor version of the current major version in use, by default. You can also specify a different minor version of the current major version in use.

MAJOR_VERSION

In this mode, the service pipeline is deployed and updated with the published, recommended (latest) major and minor version of the current template, by default. You can also specify a different major version that is higher than the major version in use and a minor version (optional).

pub fn set_deployment_type(self, input: Option<DeploymentUpdateType>) -> Self

The deployment type.

There are four modes for updating a service pipeline as described in the following. The deploymentType field defines the mode.

NONE

In this mode, a deployment doesn't occur. Only the requested metadata parameters are updated.

CURRENT_VERSION

In this mode, the service pipeline is deployed and updated with the new spec that you provide. Only requested parameters are updated. Don’t include minor or major version parameters when you use this deployment-type.

MINOR_VERSION

In this mode, the service pipeline is deployed and updated with the published, recommended (latest) minor version of the current major version in use, by default. You can also specify a different minor version of the current major version in use.

MAJOR_VERSION

In this mode, the service pipeline is deployed and updated with the published, recommended (latest) major and minor version of the current template, by default. You can also specify a different major version that is higher than the major version in use and a minor version (optional).

pub fn template_major_version(self, inp: impl Into<String>) -> Self

The major version of the service template that was used to create the service that the pipeline is associated with.

pub fn set_template_major_version(self, input: Option<String>) -> Self

The major version of the service template that was used to create the service that the pipeline is associated with.

pub fn template_minor_version(self, inp: impl Into<String>) -> Self

The minor version of the service template that was used to create the service that the pipeline is associated with.

pub fn set_template_minor_version(self, input: Option<String>) -> Self

The minor version of the service template that was used to create the service that the pipeline is associated with.

Trait Implementations

impl<C: Debug, M: Debug, R: Debug> Debug for UpdateServicePipeline<C, M, R>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.