You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2020. It is now read-only.
I have followed the steps for the serverless.js file that is to allow deployments to separate environments.
The following -
Invoking sls --env=dev will result in state files in .serverless/ being prefixed with the value of your env: Deploy.dev.json, etc. That way you can deploy unlimited environments, add pre/post processing, load whatever .env you need, etc.
Yes, I see the various state files, but when I give my dynamodb table a name in the serverless file, running a deploy for dev, then another deploy for prod will fail with
message: 'Table already exists: posts-table'
Without Serverless components, I could have posts-table-${opt:stage} to create a posts-table-dev and posts-table-prod.
How do I do this with serverless components?
The text was updated successfully, but these errors were encountered:
I have followed the steps for the serverless.js file that is to allow deployments to separate environments.
The following -
Yes, I see the various state files, but when I give my dynamodb table a name in the serverless file, running a deploy for dev, then another deploy for prod will fail with
message: 'Table already exists: posts-table'
Without Serverless components, I could have
posts-table-${opt:stage}
to create aposts-table-dev
andposts-table-prod
.How do I do this with serverless components?
The text was updated successfully, but these errors were encountered: