Hotswap doesn't update SSM parameter environment variables properly

[fongchinghinunsw]

Describe the bug

My lambda function is like the following.
new NodejsFunction(this, "some-id", { environment: { VAR1: StringParameter.valueForStringParameter(this, "/au/parameter/cool-parameter") } })

If I deploy the function before and apply hotswap, the deployment works fine. However, if I add a new environment variable to the function and use hotswap to deploy it. The value of the variable VAR1 is resolved to the path (i.e. /au/parameter/cool-parameter) instead of the true value in the parameter store.

Expected Behavior

CDK should be able to resolve the right SSM parameter value.

Current Behavior

The value of the variable VAR1 is resolved to the path (i.e. /au/parameter/cool-parameter) instead of the true value in the parameter store.

Reproduction Steps

new NodejsFunction(this, "some-id", { environment: { VAR1: StringParameter.valueForStringParameter(this, "/au/parameter/cool-parameter") } })

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.69.0

Framework Version

No response

Node.js Version

16

OS

macOS Ventura 13.2.1

Language

Typescript

Language Version

No response

Other information

No response

[pahud]

According to this, I believe hotswap has not supported SSM parameter environment variables yet. I am making this p2 feature request and please help us prioritize by upvotes.

[peterwoodworth]

@pahud In this use case, they aren't hotswapping an SSM parameter, but are instead using a dynamic references to specify an environment variable on a lambda function. When we're hotswapping, we're not using CloudFormation deploy, we're using the Lambda API

aws-cdk/packages/aws-cdk/lib/api/hotswap/lambda-functions.ts

Line 98 in d8272ef

const updateFunctionCodeResponse = await lambda.updateFunctionConfiguration(updateRequest).promise();

I'm not sure there's a good solution here that works both for CloudFormation deployments and for hotswapping

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.