pub struct UpdateServicePipeline { /* private fields */ }
Expand description
Fluent builder constructing a request to UpdateServicePipeline
.
Update the service pipeline.
There are four modes for updating a service pipeline. 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 major or minor 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 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 specify a different major version that's higher than the major version in use and a minor version.
Implementations§
source§impl UpdateServicePipeline
impl UpdateServicePipeline
sourcepub async fn customize(
self
) -> Result<CustomizableOperation<UpdateServicePipeline, AwsResponseRetryClassifier>, SdkError<UpdateServicePipelineError>>
pub async fn customize(
self
) -> Result<CustomizableOperation<UpdateServicePipeline, AwsResponseRetryClassifier>, SdkError<UpdateServicePipelineError>>
Consume this builder, creating a customizable operation that can be modified before being sent. The operation’s inner http::Request can be modified as well.
sourcepub async fn send(
self
) -> Result<UpdateServicePipelineOutput, SdkError<UpdateServicePipelineError>>
pub async fn send(
self
) -> Result<UpdateServicePipelineOutput, SdkError<UpdateServicePipelineError>>
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.
sourcepub fn service_name(self, input: impl Into<String>) -> Self
pub fn service_name(self, input: impl Into<String>) -> Self
The name of the service to that the pipeline is associated with.
sourcepub fn set_service_name(self, input: Option<String>) -> Self
pub fn set_service_name(self, input: Option<String>) -> Self
The name of the service to that the pipeline is associated with.
sourcepub fn spec(self, input: impl Into<String>) -> Self
pub fn spec(self, input: impl Into<String>) -> Self
The spec for the service pipeline to update.
sourcepub fn set_spec(self, input: Option<String>) -> Self
pub fn set_spec(self, input: Option<String>) -> Self
The spec for the service pipeline to update.
sourcepub fn deployment_type(self, input: DeploymentUpdateType) -> Self
pub fn deployment_type(self, input: DeploymentUpdateType) -> Self
The deployment type.
There are four modes for updating a service pipeline. 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 major or minor 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 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 specify a different major version that's higher than the major version in use and a minor version.
sourcepub fn set_deployment_type(self, input: Option<DeploymentUpdateType>) -> Self
pub fn set_deployment_type(self, input: Option<DeploymentUpdateType>) -> Self
The deployment type.
There are four modes for updating a service pipeline. 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 major or minor 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 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 specify a different major version that's higher than the major version in use and a minor version.
sourcepub fn template_major_version(self, input: impl Into<String>) -> Self
pub fn template_major_version(self, input: impl Into<String>) -> Self
The major version of the service template that was used to create the service that the pipeline is associated with.
sourcepub fn set_template_major_version(self, input: Option<String>) -> Self
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.
sourcepub fn template_minor_version(self, input: impl Into<String>) -> Self
pub fn template_minor_version(self, input: impl Into<String>) -> Self
The minor version of the service template that was used to create the service that the pipeline is associated with.
sourcepub fn set_template_minor_version(self, input: Option<String>) -> Self
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§
source§impl Clone for UpdateServicePipeline
impl Clone for UpdateServicePipeline
source§fn clone(&self) -> UpdateServicePipeline
fn clone(&self) -> UpdateServicePipeline
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more