-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix(apigateway): race condition between Stage and CfnAccount #18011
Conversation
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
This brings in two fixes which is reflected in the snapshot changes. See: - aws/aws-cdk#17984 - aws/aws-cdk#18011 BREAKING CHANGE: Update aws-cdk libraries to 1.137.0
This brings in two fixes which is reflected in the snapshot changes. See: - aws/aws-cdk#17984 - aws/aws-cdk#18011 BREAKING CHANGE: Update aws-cdk libraries to 1.137.0
When `cloudWatchRole` is enabled, a `CfnAccount` is created for it. Since there is no explicit dependency between the the stages and the account, CloudFormation may deploy them in the wrong order, causing the deployment to fail. Add an explicit dependency between `Stage`s (whether defined by the user or created automatically) and the CloudWatch `CfnAccount`, if it exists. Fixes aws#10722. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…n specrestapi (#22671) This PR is based off of #18011, which fixed a race condition between RestApi stages and CloudWatch roles. The mentioned PR fixed the issue for RestApi, but not SpecRestApi, which this PR aims to fix. The fix was largely implemented in RestApiBase. Since SpecRestApi inherits the same RestApiBase as RestApi, all we need to do is swap the order of resource creation so that the CloudWatch role is created before the RestApi stage, and can be attached correctly. This PR also updates the integration tests to reflect the new dependency RestApi stage has on RestApi account. Fixes #18925 ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
When
cloudWatchRole
is enabled, aCfnAccount
is created for it. Since there is no explicit dependency between the the stages and the account, CloudFormation may deploy them in the wrong order, causing the deployment to fail.Add an explicit dependency between
Stage
s (whether defined by the user or created automatically) and the CloudWatchCfnAccount
, if it exists.Fixes #10722.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license