JavaMavenWorkflow sam build fails with `[Errno 20] Not a directory` about aws-lambda-builders HOT 8 OPEN

@markusgulden sam local does not work if you point the template CodeUri the pom.xml

It seems only AWS Toolkit would work like this, which is confusing because then you have to change your template based on whether you invoke Sam from your IDE or from the cli (or have 2 different templates).

from aws-lambda-builders.

Okay so the @jaxley fix worked. Although using the base as the override in the test, (as opposed to using the target executable as the override in the buildspec), is then causing the 'Deploy serverless application' feature (when right clicking template.yml) to fail.

So to clear things up, the default CodeUri needs to be the source root with the pom, then this needs to be overridden for a deployment. This is assumed. I have still not got round to fixing this but will follow up.

from aws-lambda-builders.

Figured an explicit workaround example would be useful.

Facing the same issue,
if I give a path to pom.xml then Sam local does not work,
and if I give the path to jar then sam build does not work. Any good way to do this?

You can use a Parameter in the template.yml file and specify the correct value for a sam build using --parameter-overrides. See the docs for this: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html
Snippet from template.yaml:

Parameters:
  CodeUri:
    Description: CodeUri - change this to pom.xml directory for AWS Toolkit IDE plugin with --parameter-overrides "CodeUri"
    Type: String
    Default: lambda/target/foo.jar
Resources:
  LambdaFunction:
    Type: AWS::Serverless::Function
    Properties:
      CodeUri: !Sub ${CodeUri}
....

Invoking with sam (from project directory containing pom.xml; otherwise, choose a different directory relative to the template.yaml file location):

sam build --debug --parameter-overrides "ParameterKey=CodeUri,ParameterValue=."

from aws-lambda-builders.

You need to point the CodeUri attribute in your template.yaml to the directory with your pom.xml, not to */target/lambda.jar.
That solved the issue for me, at least.

from aws-lambda-builders.

Facing the same issue,
if I give a path to pom.xml then Sam local does not work,
and if I give the path to jar then sam build does not work. Any good way to do this?

You can use a Parameter in the template.yml file and specify the correct value for a sam build using --parameter-overrides. See the docs for this: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html

from aws-lambda-builders.

same issue here, the only way I made it work is to have my handler implement RequestHandler

from aws-lambda-builders.

Facing the same issue,
if I give a path to pom.xml then Sam local does not work,
and if I give the path to jar then sam build does not work. Any good way to do this?

from aws-lambda-builders.

I too am having this issue. Will attempt the fix mentioned. Java8 + IntelliJ + AWS Toolkit Plugin, trying to test Lambda's locally using docker containers.

from aws-lambda-builders.