S3Key of bundled lambda asset changes on every run in Github Actions workflow

[fynnfluegge]

Hi 👋,

I recently moved my cdk deployment to a workflow in github actions.

But on every run, all my lambda functions are updated during cdk deploy (even there is no change), since the S3key and the asset path of the new bundled asset differs on every run with the deployed version:

I expect that only the lambda functions, where the code has changed will be updated. I bet this has something to do with the github actions runner that causes some minor tweaks on every run which leads to a different hash of the asset path and as a result a different S3key.

Has someone bypassed this issue?

Thanks in advance!

[peterwoodworth]

I bet this has something to do with the github actions runner that causes some minor tweaks on every run which leads to a different hash of the asset path and as a result a different S3key.

This was my first thought as well, but I'm not sure exactly what would be causing this - asset hashes should remain consistent across systems. Is it possible your node version is somehow switching?

I recommend testing this on a self-hosted runner and seeing if the issue persists, that could potentially unblock you

[fynnfluegge]

It happens in this repo
👉https://github.com/fynnfluegge/rocketnotes

You can see in the "Deploy" actions that all lambda functions are updated every run. Doing cdk deploy on local machine does not update the lambda functions as expected.

[peterwoodworth]

Thanks @fynnfluegge, I'll see about reproducing this in my own repo at some point. Have you had any luck with, or been able to try the self hosted runner?

[fynnfluegge]

Thanks @peterwoodworth. I first tried to switch between Node version 17 and 18 but it has no effect. The aws-cdk global package is cached between runs by the way, so that version does not change. I don't see any more variables that could affect this for now, so going to switch to self hosted runner soon ✅

[JannikWempe]

We recently realized the same. I could not recreate the changing hashes locally but they change in a GH Action causing very long running diffs.

@fynnfluegge I am curious if you have tried a self-hosted runner or found another solution.

[AlessandroVol23]

Hey @fynnfluegge did you had any success with a self-hosted runner? We're still facing this issue unfortunately.
Thanks!