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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Bug Report
Error Description
The custom.customDomain.stage value is being ignored
Command Run
sls deploy --stage blove --region us-west-2 --verbose
Console Output
Error: V1 - Make sure the 'my.domain.com' exists.
Unable to create base path mapping for'my.domain.com':
Invalid stage identifier specified
at APIGatewayV1Wrapper.<anonymous> (<path>/node_modules/serverless-domain-manager/dist/src/aws/api-gateway-v1-wrapper.js:102:23)
at Generator.throw (<anonymous>)
at rejected (<path>/node_modules/serverless-domain-manager/dist/src/aws/api-gateway-v1-wrapper.js:6:65)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
Error: V1 - Make sure the 'my.domain.com' exists bfowr12345 blove appname-blove.
So you can see that the stage value used is the one I specified on the sls ... command line, not the one specified in the yaml file.
The API in question is a V1 rest API proxied to a lambda function with an edge domain that already exists.
The text was updated successfully, but these errors were encountered:
Community Note
Bug Report
Error Description
The
custom.customDomain.stage
value is being ignoredCommand Run
sls deploy --stage blove --region us-west-2 --verbose
Console Output
Domain Manager Configuration
Versions
Possible Solution
As a workaround you can ensure that the
provider.apiGateway.stage
value is set to${opt:stage}
instead of a static value.Additional context/Screenshots
serverless.yml
common_config.yml
To verify I changed
node_modules/serverless-domain-manager/dist/src/aws/api-gateway-v1-wrapper.js:102
to:then executed:
and got this output:
So you can see that the stage value used is the one I specified on the
sls ...
command line, not the one specified in the yaml file.The API in question is a V1 rest API proxied to a lambda function with an edge domain that already exists.
The text was updated successfully, but these errors were encountered: