You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies in advance if this is not the right place to open this issue, I don't have an extensive experience with aws-sam-local or Python, so I may be missing something really stupid.
I have a problem with my simple sam function; assuming that test.py and template.yaml are in the current folder, the issue can be reproduced by simply running echo '{}' | sam local invoke Test.
The interesting part is that running the same function without sam, everything works; assuming that test.py and template.yaml are in the current folder, you can test the following command...
Seems that your test scripts is not using standard spaces as separator (you have probably used the tab within a text editor and not a proper Python IDE). Not sure, but could be that taking quick a look at the raw file
Thanks @rafaharo , I've tried to use spaces across the test.py file, but got the same result; I suppose that - if it was an indentation issue - also the python -c command would fail.
Apologies in advance if this is not the right place to open this issue, I don't have an extensive experience with aws-sam-local or Python, so I may be missing something really stupid.
I have a problem with my simple sam function; assuming that
test.py
andtemplate.yaml
are in the current folder, the issue can be reproduced by simply runningecho '{}' | sam local invoke Test
.The error I get is
SyntaxError: invalid syntax
on lineclient = boto3.client('s3')
- full history on https://gist.github.com/maoo/2175a1c4b75a80c7271943591afb4920#file-error-logThe interesting part is that running the same function without
sam
, everything works; assuming thattest.py
andtemplate.yaml
are in the current folder, you can test the following command...... which expects to return an error saying
The specified key does not exist.
The text was updated successfully, but these errors were encountered: