Migrate won't resolve a generated TableName

[sethetter]

When 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?

[thimmig2]

Have you heard anything on this? I don't think it would be hard to add this feature and I can't really see any downsides to having it.

[kevinsperrine]

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

[vectorjohn]

Any news on this? kevinsperrine's commit looks like it will work. If no table name is present, it generates one. I mean it'd be nice to somehow tap into whatever serverless does to generate table names, but also doesn't really matter since the point of generating table names is you don't care.

[brettstack]

Is the above PR acceptable? Not sure who to tag... @rehrumesh ?

[nakshathru]

Come on maintainers!! Please accept this above PR.