-
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
Lambda: make it easier to specify a list of files and directories instead of a directory for code assets #4776
Comments
Still think we should provide first class api for this |
I don't know if this is related, but I'd like to also be able to upload a directory without zipping it. Is this feasible, already possible? |
@melnikalex check out the s3-deployment module for that. |
I just tried using this, at first it seemed to work fine, but I just realized that when I try to deploy, the latest version of my lambda is not detected. I do some changes to the file, then run either A simple SHOULD workaround is passing a different source hash everytime, here is a dummy implementation since I don't want to use this forever or calculate the hash myself: return new lambda.AssetCode(DIST_FOLDER, { exclude: ["**", `!${fileName}.js`], sourceHash: new Date().toISOString() }); then doing cdk diff does detect there is some changes, however when I run the lambda I only get the old code running... EDIT: I can confirm this is happening, I just refactored my code to adhere to the old way of doing things (packaging an entire folder) and things are working as expected, looking forward to this feature though, mighty useful if you are using webpack and packaging lambdas into a single file |
How do I whitelist a directory from exclusion? Whitelisting a file by using |
alright this worked for me
|
The |
The document is not even mention what is replacing it, just deprecate it....wat... |
I've been using this heavily and also just noticed it's been deprecated... Is there an existing alternate or one in the works? Thanks! |
Update on this? |
+1 |
1 similar comment
+1 |
This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
Still not getting the file wise assert adding feature |
Since #4473 has landed, which has support for richer
.dockerignore
patterns, there is no need for this anymore. This is very simply achieved by:You can consider adding this example somewhere if you wish, or just closing this outright.
Originally posted by @nakedible in #4428 (comment)
The text was updated successfully, but these errors were encountered: