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
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
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.
Then you could specify that explicitly for testing.
Nevertheless, the deployed stages should call the aliased functions correctly. It is only an issue with the AWS ApiGateway testing console.
changed the title [-]API Gateway integration Request has incorrect value in field **lambda function**[/-][+]Use stage variables to specify lambda qualifier in APIG[/+]on May 24, 2017
@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.
Activity
HyperBrain commentedon May 24, 2017
Good point, thank you. I will investigate the issue.
HyperBrain commentedon May 24, 2017
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.
Then you could specify that explicitly for testing.
Nevertheless, the deployed stages should call the aliased functions correctly. It is only an issue with the AWS ApiGateway testing console.
[-]API Gateway integration Request has incorrect value in field **lambda function**[/-][+]Use stage variables to specify lambda qualifier in APIG[/+]HyperBrain commentedon May 25, 2017
@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.
vkkis93 commentedon May 26, 2017
@HyperBrain brilliant work.
Thank you.
vkkis93 commentedon May 26, 2017
@HyperBrain Can you create new npm package with this fix?
HyperBrain commentedon May 26, 2017
I will publish the fix in a few moments.