Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Lambda environment change isn't picked up

See original GitHub issue

Run pulumi up on the following program:

import * as aws from "@pulumi/aws";
import * as pulumi from "@pulumi/pulumi";

const role = new aws.iam.Role("mylambda-role", {
    assumeRolePolicy: aws.iam.assumeRolePolicyForPrincipal({ Service: "lambda.amazonaws.com" }),
});

const lambda = new aws.lambda.Function("mylambda", {
    runtime: aws.lambda.DotnetCore2d1Runtime,
    code: new pulumi.asset.AssetArchive({
        ".": new pulumi.asset.FileArchive("./app/bin/Debug/netcoreapp2.1/publish"),
    }),
    timeout: 300,
    handler: "app::app.Functions::GetAsync",
    role: role.arn,
    environment: {
        variables: {
            FOO: "bar",
        },
    },
});

after the deployment succeeds, change environment to

    environment: {
        variables: {
            BUZZ: "fizz",
        },
    },

Expected: pulumi up overrides environment. Current result: preview has no changes and up deploys nothing.

Note: the env variable name has to be in UPPERCASE (may also contain _). Lowercase changes are detected.

Issue Analytics

State:
Created 4 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

barakbaron12commented, Jun 1, 2021

@pgavlin was this issue resolved in python pulumi-aws libraries? I’m seeing the same issue using pulumi-aws 3.33.0 and pulumi 2.23.1

0reactions

giladgurvichcommented, Jul 4, 2022

@pgavlin we still have this issue 😦 Pulumi doesn’t update env vars. We see it in the diff but it does not reflect the changes in AWS. We are using pulumi-aws 4.15.0 (Python) with CLI 2.25.2