-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
chore(integ-runner): use newStyleSynthesis by default #21856
chore(integ-runner): use newStyleSynthesis by default #21856
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Realistically, my eyes might have glossed over a few changes.
Having gone through them commit by commit, I think it's as close to an in-depth review as humanly possible.
aws-amplify-alpha so removing the piece that causes the failure (diff in nested stack asset hash).
Thank you for contributing! Your pull request will be updated from main 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 main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
This PR updates the `integ-runner` to _not_ set `@aws-cdk/core:newStyleStackSynthesis: false` by default. Previously this was done to cut down on the merge conflicts when the forward-merge was done between v1 and v2, but since we are now only committing to v2 it makes sense to test with `newStyleStackSynthesis` enabled. This change required re-running _all_ integration tests since using this flag changes the template. I've separated out some of the important changes into their own commits to make it easier to review. - `chore(integ-runner): use newStyleSynthesis by default` - this contains the actual change to the `integ-runner` - `integ test shapshot updates` - this contains the snapshot updates for most of the tests - The commits that mention a specific module contain fixes for broken integration tests ---- ### All Submissions: * [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/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/main/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*
This PR updates the
integ-runner
to not set@aws-cdk/core:newStyleStackSynthesis: false
by default.Previously this was done to cut down on the merge conflicts when the forward-merge was done
between v1 and v2, but since we are now only committing to v2 it makes sense to test with
newStyleStackSynthesis
enabled.This change required re-running all integration tests since using this flag changes the template. I've separated out some of the important changes into their own commits to make it easier to review.
chore(integ-runner): use newStyleSynthesis by default
- this contains the actual change to theinteg-runner
integ test shapshot updates
- this contains the snapshot updates for most of the testsAll 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