Pre-built Lambda broken on version 3.0.0, fixed in 3.0.1

[SamStephens]

Version 3.0.0 renamed the main executable file from main to bootstrap, as this is the executable the AL2023 Lambda runtime expects.

However as per #424 (comment) (thanks @yito-dev-tokyo), a required update to the scripting for using the prebuilt Lambda [*] was missed. Unfortunately by it's nature, the updates to this scripting were not testable without releasing a new version of the cdk-ecr-deployment package.

cdk-ecr-deployment/lambda/install.js

Line 48 in 0debc23

const bin = path.join(dir, 'main');

Should be

const bin = path.join(dir, 'bootstrap');

Part of the release criteria for this fix from this should be a successful deploy of the Lambda with FORCE_PREBUILT_LAMBDA enabled, to ensure there are no other bugs in the prebuilt Lambda functionality that were missed.

Workaround: to work around this bug, set the NO_PREBUILT_LAMBDA environment variable as per https://github.com/cdklabs/cdk-ecr-deployment#environment-variables to avoid the prebuilt functionality entirely.

[*] By default, the prebuilt Go executable from the Github release is downloaded and used, to avoid having to do your own build.

[SamStephens]

@scanlonp it might be worth updating the README to explain this in the meantime, or perhaps to make this a sticky issue to make it easier for users to discover the workaround.