DynamoDB Local is not available for stage when loading from file
See original GitHub issueActual Behaviour When running:
serverless dynamodb migrate --stage test
We get:
Serverless: Skipping migration: DynamoDB Local is not available for stage: test
Expected Behaviour
It would work as it used to
Steps to reproduce it
- Create a new file for dynamodb-local config, let’s call it
dynamodb-local.yml
- Add it to serverless.yml as follows:
custom:
dynamodb: ${file(./dynamodb-local.yml)}
LogCat for the issue
Serverless: Skipping migration: DynamoDB Local is not available for stage: test
Screenshots of the issue
None
Would you like to work on the issue?
Yes
temp solution the solution for me was reverting back to v0.2.35
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:7
Top Results From Across the Web
0.2.38 breaking change: DynamoDB Local is not available for ...
Solved it by adding the stage to the stages whitelist. custom: dynamodb: stages: - test ...
Read more >node.js - Serverless framework won't start with dynamodb local
I had stage set as local . So, I had to put the following line in the custom section of serverless.yml file: custom:...
Read more >[Solved] Unable to start DynamoDB Local process - Dynobase
First, make sure you have Java JDK & JRE (Java Runtime Engine) version 6.x or newer is installed on your machine since it...
Read more >Serverless Dynamodb Local Plugin
This installs the Java program locally. If using docker, this step is not required. To remove the installed dynamodb local, run: sls dynamodb...
Read more >DynamoDB local usage notes - AWS Documentation
If you omit -sharedDb , the database file is named myaccesskeyid_region.db, with the AWS access key ID and AWS Region as they appear...
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
For anyone still finding this issue, you need to add the test stage (or whatever stage you need it for) to your config:
+1! Also reverted back to v0.2.35 to avoid having to explicitly specify a stage in YAML