1 回答
- 最新
- 投票最多
- 评论最多
-1
The reason that a deployment doesn't happen is because the Deployment in the template hasn't changed. CloudFormation changes resources based on modifications to the template and because the AWS::ApiGateway::Deployment isn't updated it doesn't trigger a new deployment is triggered in APi Gateway.
You can create a new deployment or you might try updating the Description or StageDescription - I haven't tried those last two but changing them might work.
相关内容
AWS 官方已更新 3 年前- AWS 官方已更新 1 年前
- AWS 官方已更新 9 个月前
Tried everything but not working.
Did creating a new deployment in CloudFormation not work as well?
That's very unusable, since that requires editing the template for each deployment. Very bad, if you are deploying your API GW per CI/CD, as would be recommended.