-
Notifications
You must be signed in to change notification settings - Fork 4.1k
fix: deploy monitor count is off if there are > 100 changes #20067
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
Conversation
The deployment monitor failed to account for the fact the `DescribeChangeSet` operation returns a paginated output, and only represents up to 100 changes per pages. Since only the first page was considered, the progress bar would always start with a value of 101 (or less), instead of the correct count. This aggregates the `Changes` arrays from all pages of the change set description so the count is correct.
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). |
The deployment monitor failed to account for the fact the `DescribeChangeSet` operation returns a paginated output, and only represents up to 100 changes per pages. Since only the first page was considered, the progress bar would always start with a value of 101 (or less), instead of the correct count. This aggregates the `Changes` arrays from all pages of the change set description so the count is correct. Fixes aws#11805 ---- ### All Submissions: * [X] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/master/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The deployment monitor failed to account for the fact the
DescribeChangeSet
operation returns a paginated output, and onlyrepresents up to 100 changes per pages.
Since only the first page was considered, the progress bar would always
start with a value of 101 (or less), instead of the correct count.
This aggregates the
Changes
arrays from all pages of the change setdescription so the count is correct.
Fixes #11805
All Submissions:
Adding new Unconventional Dependencies:
New Features
yarn integ
to deploy the infrastructure and generate the snapshot (i.e.yarn integ
without--dry-run
)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license