Currently the @aws-cdk/aws-lambda-nodejs Functions default to OUTPUT hash type - however it'd be great to make this a configuration option to allow custom calculation of the hash to trigger a build on-demand.
Use Case
Improved deploy times when used with a Node-based async checksum algorithm for directories, or for manually triggering deploys in CI/CD based on external data.
Proposed Solution
As part of the NodejsFunction export props, re-add a bundling option for customizing the hash method & value using the existing @aws-cdk/aws-lambda#Function props. It would purely be a pass-through to the bundling.ts, optionally falling back to the current defaults - there wouldn't be any breaking changes.
This is a 🚀 Feature Request
Currently the
@aws-cdk/aws-lambda-nodejsFunctions default toOUTPUThash type - however it'd be great to make this a configuration option to allow custom calculation of the hash to trigger a build on-demand.Use Case
Improved deploy times when used with a Node-based async checksum algorithm for directories, or for manually triggering deploys in CI/CD based on external data.
Proposed Solution
As part of the
NodejsFunctionexportprops, re-add abundlingoption for customizing the hash method & value using the existing@aws-cdk/aws-lambda#Functionprops. It would purely be a pass-through to thebundling.ts, optionally falling back to the current defaults - there wouldn't be any breaking changes.This is a 🚀 Feature Request