Is your feature request related to a problem? Please describe.
With the recent change (unreleased), the lambda binary will be available in the bin folder instead of src folder.
Describe the solution you'd like
Currently in plugin.js we are fetching the built output from local/engine/flogo-web/src. When the aws lambda trigger is released, then the binary will be available in local/engine/flogo-web/src like any other binary build.
We can also think to merge the binary generation for lambda trigger (shim) build and a regular build into a single approach.
Describe alternatives you've considered
I noticed that though the binary is made available in bin folder, it is generated in src folder. The existing approach can work till the time when lambda trigger decides to delete the build output from src folder.
Is your feature request related to a problem? Please describe.
With the recent change (unreleased), the lambda binary will be available in the
binfolder instead ofsrcfolder.Describe the solution you'd like
Currently in plugin.js we are fetching the built output from
local/engine/flogo-web/src. When the aws lambda trigger is released, then the binary will be available inlocal/engine/flogo-web/srclike any other binary build.We can also think to merge the binary generation for lambda trigger (shim) build and a regular build into a single approach.
Describe alternatives you've considered
I noticed that though the binary is made available in
binfolder, it is generated insrcfolder. The existing approach can work till the time when lambda trigger decides to delete the build output from src folder.