Allow custom AWS regions for local DynamoDB instances #70
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DynamoDB local appears to segment tables by their region, and the credentials passed. Therefore, the GUI client must pass any region the user desire, and their requested credentials (Instead of randomly generating them), to access their data.
Everyone has a unique configuration, so it is hard to enforce required fields. The client does a good job at displaying errors, so end-users shouldn't be confused if there is a configuration error.
See Step 4 of the AWS documentation for running DynamoDB locally.
This should fix #68, by allowing any input to be used as a region for local connections.
I also took the liberty of fixing the remaining Linter errors while I was making these changes, there doesn't seem to be any ill-effect for doing so.