Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Migrate won't resolve a generated TableName
See original GitHub issueWhen providing raw CloudFormation code in the resources section of serverless.yml, you are able to leave out the TableName and have it default to the arn that serverless will assign it based on the format outlined here.
This is a great approach to defining table names so that your multiple stages will have their own tables, etc. Though, when trying to run sls dynamodb migrate it tells me that a missing TableName param is required.
Is this an error? Or is this a feature that needs to be added?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:10
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
FWIW, I did this. I asked about it on gitter before submitting a PR, but haven’t heard anything yet.
https://github.com/kevinsperrine/serverless-dynamodb-local/commit/9438c4d92557b9f35766bf37a2e2a7d8798d4b61
Come on maintainers!! Please accept this above PR.