-
Hi, My project structure is as below, building worked fine when building only the Cwoc.Lambda project but ever since including shared projects from the shared folder, the Please let me know of any workarounds or options to address this.
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
Under the hood,
Unfortunately, that isn't a perfect solution, since as shown in your case, the You can run One of those is However, you're using You could try moving your I see you already opened an issue with SAM, which is good. Hopefully we can prioritize either passing in extra args for .NET or set the code mount directory there. Maybe this other proposal would solve this: aws/aws-sam-cli#5546 |
Beta Was this translation helpful? Give feedback.
-
You could also try some combination of |
Beta Was this translation helpful? Give feedback.
-
Thanks Beau, that's really useful and good to know that there isn't any obvious solutions at this stage.
This way I can run Appreciate the snappy and informative response here! |
Beta Was this translation helpful? Give feedback.
-
Some extra info for you. The back door for getting parameters set to the
|
Beta Was this translation helpful? Give feedback.
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
Some extra info for you. The back door for getting parameters set to the
dotnet lambda package
is to have aaws-lambda-tools-defaults.json
file in the directory where the Lambda function is at. In there you can specify command line parameters like this.