Open ItayGarin opened 4 years ago
I believe similar issues have been reported in the past. I haven't had any cases where I've needed this so I haven't hit them myself. I was under the impression that serverless the framework used these directives to append to the packages zip.
I think where I can go next is add a case for this in the integration tests which test packaging
Sounds great! Thanks again 😊
On Fri, Jul 17, 2020, 18:09 Doug Tangren notifications@github.com wrote:
I believe similar issues have been reported in the past. I haven't had any cases where I've needed this so I haven't hit them myself. I was under the impression that serverless the framework used these directives to append to the packages zip.
I think where I can go next is add a case for this in the integration tests which test packaging
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/softprops/serverless-rust/issues/81#issuecomment-660160216, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVZPCKKYW4XT6GR4WKUM2TR4BSSHANCNFSM4O6CZRNQ .
Is there any new information on this? Currently I have the same issue 😞
Hey @softprops!
Thanks for making this awesome project! Really enjoyed following your documentation, and deploying rust lambdas :)
I stumbled across a minor issue that might have something to do with the plugin. I'd like the include a statically built executable within the output zip artifact. Though, for some reason, I wasn't able to do so.
I've tried placing the
include
keyword both in the "global" serverless.yaml scope like so -and also in my function scope like so -
FYI - I've set dockerPath to ".." since I'm building inside a workspace. Like so -
Is it just my setup? Any thoughts?