CreateDeploymentStrategyRequest

import type { CreateDeploymentStrategyRequest } from "https://aws-api.deno.dev/v0.4/services/appconfig.ts?docs=full";

interface CreateDeploymentStrategyRequest {

DeploymentDurationInMinutes: number;

Description?: string | null;

FinalBakeTimeInMinutes?: number | null;

GrowthFactor: number;

GrowthType?: GrowthType | null;

Name: string;

ReplicateTo?: ReplicateTo | null;

Tags?: {

[key: string]: string | null | undefined;

} | null;

}

§Properties

DeploymentDurationInMinutes: number

[src]

Total amount of time for a deployment to last.

Description?: string | null

[src]

A description of the deployment strategy.

FinalBakeTimeInMinutes?: number | null

[src]

Specifies the amount of time AppConfig monitors for Amazon CloudWatch alarms after the configuration has been deployed to 100% of its targets, before considering the deployment to be complete. If an alarm is triggered during this time, AppConfig rolls back the deployment. You must configure permissions for AppConfig to roll back based on CloudWatch alarms. For more information, see Configuring permissions for rollback based on Amazon CloudWatch alarms in the AppConfig User Guide.

GrowthFactor: number

[src]

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

GrowthType?: GrowthType | null

[src]

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 dividing the total number of targets by the value specified for Step percentage. For example, a linear deployment that uses a Step percentage of 10 deploys the configuration to 10 percent of the hosts. After those deployments are complete, the system deploys the configuration to the next 10 percent. This continues until 100% of the targets have successfully received the 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.

Name: string

[src]

A name for the deployment strategy.

ReplicateTo?: ReplicateTo | null

[src]

Save the deployment strategy to a Systems Manager (SSM) document.

Tags?: {

[key: string]: string | null | undefined;

} | null

[src]

Metadata to assign to the deployment strategy. Tags help organize and categorize your AppConfig resources. Each tag consists of a key and an optional value, both of which you define.