Hello,
I hope this message finds you well. I'm working on a project using the AWS CloudFormation to deploy Lambda functions and API Gateway. While most of the deployment process has been smooth, I've encountered an issue related to updating the API Gateway stage when deploying a Lambda function's new version.
Problem:
After deploying a new version of my Lambda function using the CloudFormation, I noticed that the changes are not reflected in the associated API Gateway stage. The API Gateway stage deployment is not triggered, even though the deployment was successful.
Details:
I'm using Python-based Lambda functions.
The CDK stack includes the Lambda function, API Gateway, and the necessary integration.
The CDK deploy command runs without errors, indicating a successful deployment. I have AutoDeploy set to true in the Deployment in the YAML Template.
Expected Behavior:
I expect that when I deploy a new version of the Lambda function using CDK, the associated API Gateway stage should automatically update to use the latest version of the Lambda function.
AWS OFFICIALUpdated 10 months ago
Usually I trigger it by applying a change in the Stage description in the template. that's why I always include the date in the description.