generated template.yml doesn't work with `sam local start-api`
See original GitHub issueUsing the same serverless.yml
as #12, when I run sam local start-api
I get the error:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1702c38]
goroutine 1 [running]:
main.start(0xc42008d040)
/root/go/src/github.com/awslabs/aws-sam-local/start.go:122 +0xe18
github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli.HandleAction(0x17d56e0, 0x19d02a0, 0xc42008d040, 0xc4202d3e00, 0x0)
/root/go/src/github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli/app.go:487 +0x7c
github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli.Command.Run(0x19a5845, 0x9, 0x0, 0x0, 0x0, 0x0, 0x0, 0x19cde2e, 0x3c9, 0x0, ...)
/root/go/src/github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli/command.go:207 +0xb72
github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli.(*App).RunAsSubcommand(0xc4204e6340, 0xc42008ca00, 0x0, 0x0)
/root/go/src/github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli/app.go:374 +0xacc
github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli.Command.startApp(0x19a2d5c, 0x5, 0x0, 0x0, 0x0, 0x0, 0x0, 0x19ca20b, 0x47, 0x0, ...)
/root/go/src/github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli/command.go:293 +0x8a3
github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli.Command.Run(0x19a2d5c, 0x5, 0x0, 0x0, 0x0, 0x0, 0x0, 0x19ca20b, 0x47, 0x0, ...)
/root/go/src/github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli/command.go:93 +0x14c7
github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli.(*App).Run(0xc420491d40, 0xc42000e2d0, 0x3, 0x3, 0x0,0x0)
/root/go/src/github.com/awslabs/aws-sam-local/vendor/github.com/codegangsta/cli/app.go:250 +0x7d0
main.main()
/root/go/src/github.com/awslabs/aws-sam-local/main.go:375 +0x24a2
I’m using SAM version 0.2.4
.
The only way I have found to “fix it” is to remove both the BigMouth
CFN resource, as well as all references to it in the template.yml. I appreciate this is probably problem with SAM local, but I’m just wondering if you have any insight into what might be the problem.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
sam local start-api - AWS Serverless Application Model
The AWS SAM CLI first tries to locate a template file built using the sam build command, located in the .aws-sam subfolder, and...
Read more >sam local start-api --static-dir doesn't serve anything after ...
The AWS SAM CLI first tries to locate a template file built using the sam build command, located in the .aws-sam subfolder, and...
Read more >Tutorial: Deploying a Hello World application
In this guide, you download, build, and deploy a sample Hello World application using Amazon SAM. You then test the application in the...
Read more >Using AWS SAM-CLI requires rebuild every time I update ...
Essentially run: sam local start-api -t template.yaml --skip-pull-image. This got hot reloading working for me.
Read more >Tag Archives: AWS SAM
sam build --use-container && sam local start-api 2>&1 | tr "\r" "\n" ... To start, these are the resources that you'll need in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve submitted a pull request to fix the issue in SAM local. I’ll let you know once it’s merged and published.
The issue was merged. Closing this.