0.2.38 breaking change: DynamoDB Local is not available for stage
See original GitHub issueIt looks like you released a new patch version and I don’t see any release notes or instructions. This change was a breaking change for us in CI. We now get:
Actual 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 did before or be released as a new minor or major version with migration instructions.
Steps to reproduce it
See above
LogCat for the issue
See above
Screenshots of the issue
None
Would you like to work on the issue?
No thank you
Issue Analytics
- State:
- Created 4 years ago
- Reactions:21
- Comments:12
Top Results From Across the Web
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...
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 >Can you change DynamoDB Schemas? - YouTube
We go over how to migrate your data in DynamoDB when your schema changes. ... Live chat replay is not available for this...
Read more >serverless-dynamodb-local - bytemeta
serverless-dynamodb-local repo issues. ... 0.2.38 breaking change: DynamoDB Local is not available for stage. michinamibia. michinamibia OPEN.
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
Solved it by adding the stage to the stages whitelist.
For all stages: