Skip to content
This repository was archived by the owner on May 1, 2020. It is now read-only.
This repository was archived by the owner on May 1, 2020. It is now read-only.

Deploying different environments #14

@veloware

Description

@veloware

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions