-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: V2 - Unable to update base path mapping for '...': Invalid stage identifier specified #589
Comments
Hi @jsw Please set the More info is here: https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-stages.html |
Hi @rddimon Thanks for the response. Can you elaborate at bit? You want me to change Did something change between 7.0.4 and 7.1.0 that requires me to update serverless.xml? I explicitly set the stage in each of my environments, e.g. |
I second this issue, and I can confirm that setting However it'll only deploy to our stg environment, it fails to deploy afterwards to prod.
|
I'm getting a similar issue related to v7.1.0 where I can't deploy to prod after deploying to staging with the following error:
|
In 7.1.0 we released a fix for the issue #578 It looks like, from the AWS documentation, that for the To simply fix your issue you will need just to remove |
Thank you for highlighting it! |
I am seeing this error - was it supposed to be resolved in the latest update? I just updated to v7.1.1 today and started seeing this issue. Will try the fix above but curious if there is something else I need to do. |
Upgrading to customDomain:
domainName: ${env:DOMAIN, ''}
stage: $default
basePath: v3/loans
apiType: http
endpointType: regional |
Thank you for the response @belferink1996! Our issue ended up being another result of updating with the aws sdk. I can confirm that the $default stage with version 7.1.1 does work. Thanks! |
maybe this should've been a major change, if the API is not compatible with the previous one? |
Hi @zoli-kasa It was a bit tricky release as it was a bug fix for the #578. This issue is related only to the HTTP API type and not to the REST or Websocket. But in general, the concern is right and we will take it into account in our further releases. |
Hi @jsw Is the issue solved for you now? Are we good to close the issue? |
maybe you could write a detailed change about this in the release log, to help other users with the same issue during upgrade? |
I have confirmed that removing |
It might be harder to predict issues |
Community Note
Bug Report
Error Description
After upgrading from 7.0.4 to 7.1.0 I get the following output
Command Run
Console Output
Domain Manager Configuration
Replace this with your own
serverless.yml
file (anonymized, of course) to help us better resolve your issue.Versions
The text was updated successfully, but these errors were encountered: