ForceNewDeploymentProperty Struct
Determines whether to force a new deployment of the service.
By default, deployments aren't forced. You can use this option to start a new deployment with no service definition changes. For example, you can update a service's tasks to use a newer Docker image with the same image/tag combination ( my_image:latest ) or to roll Fargate tasks onto a newer platform version.
Example
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import { aws_ecs as ecs } from 'aws-cdk-lib';
const forceNewDeploymentProperty: ecs.CfnService.ForceNewDeploymentProperty = {
enableForceNewDeployment: false,
// the properties below are optional
forceNewDeploymentNonce: 'forceNewDeploymentNonce',
};
Properties
enableForceNewDeploymentboolean | IResolvableenable_force_new_deploymenttyping.Union[bool, IResolvable]enableForceNewDeploymentBooleanEnableForceNewDeploymentboolEnableForceNewDeploymentinterface{}required#notes
By default, deployments aren't forced. You can use this option to start a new deployment with no service definition changes. For example, you can update a service's tasks to use a newer Docker image with the same image/tag combination ( my_image:latest ) or to roll Fargate tasks onto a newer platform version.
forceNewDeploymentNoncestringforce_new_deployment_noncestrforceNewDeploymentNonceStringForceNewDeploymentNoncestringForceNewDeploymentNonce*string#notes
The value must be a unique, time- varying value like a timestamp, random string, or sequence number. Use this property when you want to ensure your tasks pick up the latest version of a Docker image that uses the same tag but has been updated in the registry.