-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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: add new style integration test snapshots #19802
chore: add new style integration test snapshots #19802
Conversation
The bulk of this PR is adding the new style integration test snapshots that the new `integ-runner` uses. These are snapshots of the cloud assembly and have folder names like `${testName}.integ.snapshot`. Some other minor updates were made as part of this change. 1. Updated `integ-runner` to use `synthFast` instead of `synth` to speed up performance. 2. Make sure the `integ-runner` throws an exit code if any tests fail 3. Updated the test names to include the directory if running from a parent directory (i.e. `packages/@aws-cdk`). 4. Added the ability to exempt from the update workflow (update workflow is not yet implemented). If a test is exempt then the snapshot will not contain any assets. For now this is used for tests that include very large assets that would drastically increase the size of the repo. 5. Updated some custom resources to exclude `*.ts` files from the asset bundle. `.ts` files are already excluded when we publish (`.d.ts` files are not), and `.js` files are the only thing needed by the Lambda function anyway. This was causing issues when running a build because those files in the snapshot would cause `tsc` to fail. - Updated: `aws-events-targets/lib/aws-api.ts` `aws-redshift/lib/private/database-query.ts` `aws-stepfunctions-tasks/lib/evaluate-expression.ts` `custom-resources/lib/aws-custom-resource/aws-custom-resource.ts` `custom-resources/lib/provider-framework/provider.ts`
1. remove `.cache` directories from the snapshot 2. cleanup `manifest.json` in snapshots, removing trace data
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 PR is a follow up to #19802 which added all of the new integ test snapshots that are used by the new `integ-runner` tool. This PR switches out the old `cdk-integ` tool for the new `integ-runner`. Updates made: 1. Update all `package.json` files to install and use the `integ-runner` 2. Update `cdk-test` to use `integ-runner` 3. Updates snapshots for 2 tests that were changed since #19802 was merged. ---- ### All Submissions: * [ ] 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 `cdk-integ` to deploy the infrastructure and generate the snapshot (i.e. `cdk-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 bulk of this PR is adding the new style integration test snapshots that the new `integ-runner` uses. These are snapshots of the cloud assembly and have folder names like `${testName}.integ.snapshot`. Some other minor updates were made as part of this change. 1. Updated `integ-runner` to use `synthFast` instead of `synth` to speed up performance. 2. Make sure the `integ-runner` throws an exit code if any tests fail 3. Updated the test names to include the directory if running from a parent directory (i.e. `packages/@aws-cdk`). 4. Added the ability to exempt from the update workflow (update workflow is not yet implemented). If a test is exempt then the snapshot will not contain any assets. For now this is used for tests that include very large assets that would drastically increase the size of the repo. 5. Updated some custom resources to exclude `*.ts` files from the asset bundle. `.ts` files are already excluded when we publish (`.d.ts` files are not), and `.js` files are the only thing needed by the Lambda function anyway. This was causing issues when running a build because those files in the snapshot would cause `tsc` to fail. - Updated: `aws-events-targets/lib/aws-api.ts` `aws-redshift/lib/private/database-query.ts` `aws-stepfunctions-tasks/lib/evaluate-expression.ts` `custom-resources/lib/aws-custom-resource/aws-custom-resource.ts` `custom-resources/lib/provider-framework/provider.ts` ---- ### 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 * [x] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/master/INTEGRATION_TESTS.md)? * [x] Did you use `cdk-integ` to deploy the infrastructure and generate the snapshot (i.e. `cdk-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 is a follow up to #19802 which added all of the new integ test snapshots that are used by the new `integ-runner` tool. This PR switches out the old `cdk-integ` tool for the new `integ-runner`. Updates made: 1. Update all `package.json` files to install and use the `integ-runner` 2. Update `cdk-test` to use `integ-runner` 3. Updates snapshots for 2 tests that were changed since #19802 was merged. ---- ### All Submissions: * [ ] 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 `cdk-integ` to deploy the infrastructure and generate the snapshot (i.e. `cdk-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 bulk of this PR is adding the new style integration test snapshots that the new `integ-runner` uses. These are snapshots of the cloud assembly and have folder names like `${testName}.integ.snapshot`. Some other minor updates were made as part of this change. 1. Updated `integ-runner` to use `synthFast` instead of `synth` to speed up performance. 2. Make sure the `integ-runner` throws an exit code if any tests fail 3. Updated the test names to include the directory if running from a parent directory (i.e. `packages/@aws-cdk`). 4. Added the ability to exempt from the update workflow (update workflow is not yet implemented). If a test is exempt then the snapshot will not contain any assets. For now this is used for tests that include very large assets that would drastically increase the size of the repo. 5. Updated some custom resources to exclude `*.ts` files from the asset bundle. `.ts` files are already excluded when we publish (`.d.ts` files are not), and `.js` files are the only thing needed by the Lambda function anyway. This was causing issues when running a build because those files in the snapshot would cause `tsc` to fail. - Updated: `aws-events-targets/lib/aws-api.ts` `aws-redshift/lib/private/database-query.ts` `aws-stepfunctions-tasks/lib/evaluate-expression.ts` `custom-resources/lib/aws-custom-resource/aws-custom-resource.ts` `custom-resources/lib/provider-framework/provider.ts` ---- ### 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 * [x] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/master/INTEGRATION_TESTS.md)? * [x] Did you use `cdk-integ` to deploy the infrastructure and generate the snapshot (i.e. `cdk-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 is a follow up to aws#19802 which added all of the new integ test snapshots that are used by the new `integ-runner` tool. This PR switches out the old `cdk-integ` tool for the new `integ-runner`. Updates made: 1. Update all `package.json` files to install and use the `integ-runner` 2. Update `cdk-test` to use `integ-runner` 3. Updates snapshots for 2 tests that were changed since aws#19802 was merged. ---- ### All Submissions: * [ ] 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 `cdk-integ` to deploy the infrastructure and generate the snapshot (i.e. `cdk-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 bulk of this PR is adding the new style integration test snapshots
that the new
integ-runner
uses. These are snapshots of the cloudassembly and have folder names like
${testName}.integ.snapshot
.Some other minor updates were made as part of this change.
integ-runner
to usesynthFast
instead ofsynth
to speedup performance.
integ-runner
throws an exit code if any tests failparent directory (i.e.
packages/@aws-cdk
).is not yet implemented). If a test is exempt then the snapshot will
not contain any assets. For now this is used for tests that include
very large assets that would drastically increase the size of the
repo.
*.ts
files from the assetbundle.
.ts
files are already excluded when we publish (.d.ts
files are not), and
.js
files are the only thing needed by theLambda function anyway. This was causing issues when running a build
because those files in the snapshot would cause
tsc
to fail.aws-events-targets/lib/aws-api.ts
aws-redshift/lib/private/database-query.ts
aws-stepfunctions-tasks/lib/evaluate-expression.ts
custom-resources/lib/aws-custom-resource/aws-custom-resource.ts
custom-resources/lib/provider-framework/provider.ts
All Submissions:
Adding new Unconventional Dependencies:
New Features
cdk-integ
to deploy the infrastructure and generate the snapshot (i.e.cdk-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