- 최신
- 최다 투표
- 가장 많은 댓글
There is only one API definition that can be deployed to multiple stages. You change the definition and then you deploy. You can't really change the API that is deployed, unless you deploy again.
To achieve what you want, you need to use stage variables. So you will create a variable and in each stage you will give it a different name. The integration will use the stage variable as part of the definition. For example, you can have a stage variable called functionName. In stage v1 the value will be Function1. in stage v2 the value will be Function2. In the integration configuration you will use ${stageVariables.functioName} in place of the function name. You can find more information here.
Thanks! I had read the documentation about this when I posed the question, but what what misled me was the dropdown at the very top of the Routes and Integrations screens in the console. They appear to let you select a stage for a set of routes or integrations, but the drop-down is grayed out. I'm not sure why they're there, and thought perhaps there was something I was missing to enable them.
I understand what you are saying about stage variables. I'll do that.
관련 콘텐츠
- AWS 공식업데이트됨 10달 전