Don't wait for Lambda deployment

When deploying a Lambda through CodeDeploy configure with, for example, LINEAR_10PERCENT_EVERY_10MINUTES, CDK will block waiting for the deployment to finish (and display the message “CodeDeploy deployment started”.

CDK should just start the deployment and not wait for it to finish, since failing a Lambda deployment (and rolling it back) should have no bearing on the rest of the CDK deployment.

Reproduction Steps

const lambdaName = basename(__dirname)

export async function myLambda(stack: Stack): Promise<Alias> {
    const f = new Function(stack, lambdaName, {
        runtime: Runtime.GO_1_X,
        handler: "main",
        code: Code.asset(join(__dirname, "lambda.zip")),
    })

    const alias = new Alias(stack, lambdaName + "-alias", {
        aliasName: "live",
        version: f.addVersion(2),
    })

    new LambdaDeploymentGroup(stack, lambdaName + "-deployment", {
        alias: alias,
        deploymentConfig: LambdaDeploymentConfig.LINEAR_10PERCENT_EVERY_10MINUTES,
    })

    return alias
}

Error Log

CDK blocks in the UPDATE_IN_PROGRESS stage.

Environment

• **CLI Version : 1.18.0
• **Framework Version: 1.18.0
• **OS : macOS Catalina
• **Language : Typescript

Other

---

This is 🐛 Bug Report

[duarten]

The advantage would be to only have to deal with CDK and no other tool. Ideally, I could specify which stacks to wait for and which to fire-and-forget (and I wouldn’t mind contributing this code). Even more ideally, CDK could have hooks that would allow me to specify this programmatically, so that I could for example wait for a deployment only until CodeDeploy is done with the pre-traffic tests.

[KyleMuellerPFG]

I’d be interested in this "fire-and-forget’ avenue to support deployments of apps that contain stacks provisioning AWS Certificates, as certificates aren’t “complete” until validated, a process that could potentially take a lot of time if it involves e-mail validation, and I don’t want to hang up the rest of the deployment.