pub struct Builder { /* private fields */ }
Expand description
A builder for UpdateServicePipelineInput
.
Implementations§
source§impl Builder
impl Builder
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.
sourcepub fn build(self) -> Result<UpdateServicePipelineInput, BuildError>
pub fn build(self) -> Result<UpdateServicePipelineInput, BuildError>
Consumes the builder and constructs a UpdateServicePipelineInput
.
Examples found in repository?
8809 8810 8811 8812 8813 8814 8815 8816 8817 8818 8819 8820 8821 8822 8823 8824 8825 8826 8827 8828 8829 8830 8831 8832 8833 8834 8835 8836 8837 8838 8839 8840 8841 8842 8843 8844 8845 8846 8847 8848 8849 8850 8851
pub async fn customize(
self,
) -> std::result::Result<
crate::operation::customize::CustomizableOperation<
crate::operation::UpdateServicePipeline,
aws_http::retry::AwsResponseRetryClassifier,
>,
aws_smithy_http::result::SdkError<crate::error::UpdateServicePipelineError>,
> {
let handle = self.handle.clone();
let operation = self
.inner
.build()
.map_err(aws_smithy_http::result::SdkError::construction_failure)?
.make_operation(&handle.conf)
.await
.map_err(aws_smithy_http::result::SdkError::construction_failure)?;
Ok(crate::operation::customize::CustomizableOperation { handle, operation })
}
/// 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](aws_smithy_types::retry::RetryConfig), which can be
/// set when configuring the client.
pub async fn send(
self,
) -> std::result::Result<
crate::output::UpdateServicePipelineOutput,
aws_smithy_http::result::SdkError<crate::error::UpdateServicePipelineError>,
> {
let op = self
.inner
.build()
.map_err(aws_smithy_http::result::SdkError::construction_failure)?
.make_operation(&self.handle.conf)
.await
.map_err(aws_smithy_http::result::SdkError::construction_failure)?;
self.handle.client.call(op).await
}