Clarification on create_table limitations and intent

[whitfin]

I saw that the README states that create_table is only meant for testing, but I'm curious if this is due to it not being ready "for production" or because it's never intended to be ready for production?

The obvious feature to add is BILLING_MODE, and I was going to look into doing this, but it occurred to me that it might be intentionally left out. Same for LSI. As both of these are support by the DynamoDB client, I figure it's something like API limitations and/or maintenance limitations?

In my current workflow (using the Serverless framework) I can either define my tables in code, or define them in CloudFormation. Doing so in CloudFormation is quite tedious, but doing it in code is a bit awkward as it's not supported by dyntastic.

Any clarification you can provide here is appreciated!

[nayaverdier]

@whitfin No reason aside from production readiness (and less demand than the other features). I only really implemented create_table for running the CI tests, but any PRs to improve the functionality + make it more complete/robust would be appreciated!