Added to existing repo, causes stageName already exists

[camhart]

 Serverless Error ---------------------------------------

     An error occurred while provisioning your stack: ApiGatewayStage
     - myStageName already exists.

  Stack Trace --------------------------------------------

Not sure if there is anyway to get around this....

I just did sls remove, and then sls deploy and it resolved it. But you can't just do that everytime.

[paulSambolin]

My first issue! Thanks for posting, I can't work on a fix until this weekend as I am traveling but could you provide some more info? Serverless version, did you make any changes to the code before re-deploying?, and anything else you think might be relevant.

[camhart]

Reproduction steps:

1. mkdir testing
2. cd testing
3. sls create -t aws-nodejs
4. add an http event to the function:

    events:
      - http:
          path: hello
          method: get

5. sls deploy
6. npm install serverless-enable-api-logs
7. make changes to serverless.yml--enable plugin.

plugins:
  - serverless-enable-api-logs

8. sls deploy

Error:

............Serverless: Deployment failed!

  Serverless Error ---------------------------------------

     An error occurred while provisioning your stack: ApiGatewayStage
     - dev already exists.

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues

  Your Environment Information -----------------------------
     OS:                 win32
     Node Version:       6.9.2
     Serverless Version: 1.5.0

I don't know how easy this will be to fix. From what I can tell, once you deploy using a CloudFormation Deployment using the stageName, you can't deploy using a Stage resource that has the same stageName... This might be something that needs taken up with AWS.