Hi,
i’m trying to run a sls dynamodb migrate command on a dynamodb installed in a container?
serverless seems not to execute the migration script on the container - but instead starts running dynamodb locally (I think). I have no idea how to connect to that local instance (as port 8000 is already used by the container)
I specified in the config however that starting a local DB should not happen.
serverless.yml :
custom:
dynamodb:
stages:
- dev
start:
host : localhost
port: 8000
noStart: true
migrate: true
seed: true
convertEmptyValues: true
On the dynamo running in the docker nothing got created.
If I run sls dynamodb remove // followed by a sls dynamodb migratie - it tells me “table already exists”. How come - I just removed the DB…
C:\Code\VAZG\UserManagement\vazg-msa-userservice>sls dynamodb remove
Serverless: Running “serverless” installed locally (in service node_modules)
Serverless: Configuration warning at ‘org’: should match pattern “^[a-z0-9]{5,39}$”
Serverless:
Serverless: Learn more about configuration validation here:
Serverless:
Serverless: Deprecation warning: Starting with next major version, default value of provider.lambdaHashingVersion will be equal to “20201221”
More Info:
Successfully removed dynamodb local!
C:\Code\VAZG\UserManagement\vazg-msa-userservice>sls dynamodb migrate
Serverless: Running “serverless” installed locally (in service node_modules)
Serverless: Configuration warning at ‘org’: should match pattern “^[a-z0-9]{5,39}$”
Serverless:
Serverless: Learn more about configuration validation here:
Serverless:
Serverless: Deprecation warning: Starting with next major version, default value of provider.lambdaHashingVersion will be equal to “20201221”
More Info:
Serverless: DynamoDB - Warn - table UserAllocatie-dev already exists
Serverless: DynamoDB - Warn - table AllocatieRefData-dev already exists