Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deploy fails with "pathmapping - Invalid stage identifier specified"

See original GitHub issue

I can’t seem to add serverless-api-stage to a project which contains the serverless-domain-manager plugin. Deployment fails with the error:

...
Serverless: Uploading CloudFormation file to S3...
Serverless: Uploading artifacts...
Serverless: Uploading service .zip file to S3 (15.76 MB)...
Serverless: Validating template...
Serverless: Updating Stack...
Serverless: Checking Stack update progress...
..........................................
Serverless: Operation failed!

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

  An error occurred: pathmapping - Invalid stage identifier specified.

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Forums:        forum.serverless.com
     Chat:          gitter.im/serverless/serverless

  Your Environment Information -----------------------------
     OS:                     darwin
     Node Version:           9.3.0
     Serverless Version:     1.26.1

I’ve narrowed it down to an interaction between the two plugins.

Here’s a repo which demonstrates the issue:

https://github.com/aneilbaboo/serverless-api-stage-issue

Note:

I cross-posted this issue to serverless-api-stage.
This comment hints at a potential solution: https://github.com/serverless/serverless/issues/4029#issuecomment-386045929

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:8 (2 by maintainers)

Top GitHub Comments

2reactions

captainsiddcommented, Mar 1, 2019

Hi there! This issue should be fixed in version 3.1.0, since we no longer create the basepath mapping through CloudFormation.

Let us know if you’re still experiencing this problem - the pathmapping resource should never exist in CloudFormation once you’ve migrated to 3.1.0.

1reaction

alemayehutlhncommented, May 7, 2019

Version 3.1.0 and above fixed the issue related to bathpathmapping.