-
Notifications
You must be signed in to change notification settings - Fork 68
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
Use stage variables to specify lambda qualifier in APIG #40
Comments
Good point, thank you. I will investigate the issue. |
I set a stage variable SERVERLESS_ALIAS that equals the deployed stage, so if I would set it to getUser:${SERVERLESS_ALIAS} it should work. Nevertheless, the deployed stages should call the aliased functions correctly. It is only an issue with the AWS ApiGateway testing console. |
@vkkis93 This was indeed a great idea 🙌 I changed the qualifier/alias to the stage variable and tested it with two different aliases. It would be good, if you also give it a try with the alias plugin master branch. |
@HyperBrain brilliant work. |
@HyperBrain Can you create new npm package with this fix? |
I will publish the fix in a few moments. |
On Integration request page field lambda function always has value of last deployed stage.
For Example
getUser:staging or getUser:production.
I think it should be like getUser:${functionAlias}
Where functionAlias value should be specified in stage variables tab
The text was updated successfully, but these errors were encountered: