-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(aws-lambda-nodejs): CUSTOM
hash pass-through
#16157
Labels
@aws-cdk/aws-lambda-nodejs
effort/medium
Medium work item – several days of effort
feature-request
A feature should be added or improved.
p2
Comments
devlsh
added
feature-request
A feature should be added or improved.
needs-triage
This issue or PR still needs to be triaged.
labels
Aug 21, 2021
jogold
added a commit
to jogold/aws-cdk
that referenced
this issue
Sep 8, 2021
Add a `assetHash` prop to customize the asset hash. Closes aws#16157
jogold
added a commit
to jogold/aws-cdk
that referenced
this issue
Sep 8, 2021
Add a `assetHash` prop to customize the asset hash. Closes aws#16157
nija-at
added
effort/medium
Medium work item – several days of effort
p2
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Oct 5, 2021
mergify bot
pushed a commit
that referenced
this issue
Nov 8, 2021
By default the asset hash for a `NodejsFunction` is based on the bundling output, the result of the `esbuild` bundling. Add a `assetHash` prop to customize the asset hash and allow users to implement their own logic. This can be useful if users want to invalidate the asset based on specific (input) file contents or logic. Closes #16157 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
TikiTDO
pushed a commit
to TikiTDO/aws-cdk
that referenced
this issue
Feb 21, 2022
By default the asset hash for a `NodejsFunction` is based on the bundling output, the result of the `esbuild` bundling. Add a `assetHash` prop to customize the asset hash and allow users to implement their own logic. This can be useful if users want to invalidate the asset based on specific (input) file contents or logic. Closes aws#16157 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-lambda-nodejs
effort/medium
Medium work item – several days of effort
feature-request
A feature should be added or improved.
p2
Currently the
@aws-cdk/aws-lambda-nodejs
Functions default toOUTPUT
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
exportprops
, re-add abundling
option for customizing the hash method & value using the existing@aws-cdk/aws-lambda#Function
props. 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
The text was updated successfully, but these errors were encountered: