Struct UpdateDeploymentStrategyInput 

#[non_exhaustive]
pub struct UpdateDeploymentStrategyInput {
    pub deployment_strategy_id: Option<String>,
    pub description: Option<String>,
    pub deployment_duration_in_minutes: Option<i32>,
    pub final_bake_time_in_minutes: Option<i32>,
    pub growth_factor: Option<f32>,
    pub growth_type: Option<GrowthType>,
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

deployment_strategy_id: Option<String>

The deployment strategy ID.

description: Option<String>

A description of the deployment strategy.

deployment_duration_in_minutes: Option<i32>

Total amount of time for a deployment to last.

final_bake_time_in_minutes: Option<i32>

The amount of time that AppConfig monitors for alarms before considering the deployment to be complete and no longer eligible for automatic rollback.

growth_factor: Option<f32>

The percentage of targets to receive a deployed configuration during each interval.

growth_type: Option<GrowthType>

The algorithm used to define how percentage grows over time. AppConfig supports the following growth types:

Linear: For this type, AppConfig processes the deployment by increments of the growth factor evenly distributed over the deployment time. For example, a linear deployment that uses a growth factor of 20 initially makes the configuration available to 20 percent of the targets. After 1/5th of the deployment time has passed, the system updates the percentage to 40 percent. This continues until 100% of the targets are set to receive the deployed configuration.

Exponential: For this type, AppConfig processes the deployment exponentially using the following formula: G*(2^N). In this formula, G is the growth factor specified by the user and N is the number of steps until the configuration is deployed to all targets. For example, if you specify a growth factor of 2, then the system rolls out the configuration as follows:

2*(2^0)

2*(2^1)

2*(2^2)

Expressed numerically, the deployment rolls out as follows: 2% of the targets, 4% of the targets, 8% of the targets, and continues until the configuration has been deployed to all targets.

Implementations

impl UpdateDeploymentStrategyInput

pub fn deployment_strategy_id(&self) -> Option<&str>

The deployment strategy ID.

pub fn description(&self) -> Option<&str>

A description of the deployment strategy.

pub fn deployment_duration_in_minutes(&self) -> Option<i32>

Total amount of time for a deployment to last.

pub fn final_bake_time_in_minutes(&self) -> Option<i32>

The amount of time that AppConfig monitors for alarms before considering the deployment to be complete and no longer eligible for automatic rollback.

pub fn growth_factor(&self) -> Option<f32>

The percentage of targets to receive a deployed configuration during each interval.

pub fn growth_type(&self) -> Option<&GrowthType>

The algorithm used to define how percentage grows over time. AppConfig supports the following growth types:

Linear: For this type, AppConfig processes the deployment by increments of the growth factor evenly distributed over the deployment time. For example, a linear deployment that uses a growth factor of 20 initially makes the configuration available to 20 percent of the targets. After 1/5th of the deployment time has passed, the system updates the percentage to 40 percent. This continues until 100% of the targets are set to receive the deployed configuration.

Exponential: For this type, AppConfig processes the deployment exponentially using the following formula: G*(2^N). In this formula, G is the growth factor specified by the user and N is the number of steps until the configuration is deployed to all targets. For example, if you specify a growth factor of 2, then the system rolls out the configuration as follows:

2*(2^0)

2*(2^1)

2*(2^2)

Expressed numerically, the deployment rolls out as follows: 2% of the targets, 4% of the targets, 8% of the targets, and continues until the configuration has been deployed to all targets.

impl UpdateDeploymentStrategyInput

pub fn builder() -> UpdateDeploymentStrategyInputBuilder

Creates a new builder-style object to manufacture UpdateDeploymentStrategyInput.

Trait Implementations

impl Clone for UpdateDeploymentStrategyInput

fn clone(&self) -> UpdateDeploymentStrategyInput

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for UpdateDeploymentStrategyInput

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

Formats the value using the given formatter.

impl PartialEq for UpdateDeploymentStrategyInput

fn eq(&self, other: &UpdateDeploymentStrategyInput) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for UpdateDeploymentStrategyInput