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
I am running SAM CLI, version 1.36.0 and when I try to input the architectures prompted by Cookiecutter I get an Error: Unable to decode to JSON. error. And this might not be intuitive for a first time user
sam init --location cookiecutter-aws-sam-eventbridge-hello-java-gradle
project_name [Your EventBridge Starter app]: x
runtime [java11]:
architectures [default]: arm64
Error: Unable to decode to JSON.
Work around
If I set the input to {"value":["arm64"]} for architectures then this works.
sam init --location cookiecutter-aws-sam-eventbridge-hello-java-gradle
project_name [Your EventBridge Starter app]: x
runtime [java11]:
architectures [default]: {"value":["arm64"]}
Or if I pass in architecture in the cli and not enter anything in architectures:
sam init --location java11/cookiecutter-aws-sam-eventbridge-hello-java-gradle --architecture arm64
Possible Solution
Change the architectures in cookiecutter.json to be a simple string value like runtime, this would mean change all of the templates and CLI
The text was updated successfully, but these errors were encountered:
since we only have 2 types of supported architecture x86_64 and arm64. May we suggest user key in x86_64 or arm64 or both?
If both is selected then we generate an array of 2 elements in the generated yaml template
Issue
I am running
SAM CLI, version 1.36.0
and when I try to input thearchitectures
prompted by Cookiecutter I get anError: Unable to decode to JSON.
error. And this might not be intuitive for a first time userWork around
If I set the input to
{"value":["arm64"]}
forarchitectures
then this works.Or if I pass in
architecture
in the cli and not enter anything inarchitectures
:Possible Solution
architectures
incookiecutter.json
to be a simple string value likeruntime
, this would mean change all of the templates and CLIThe text was updated successfully, but these errors were encountered: