-
Notifications
You must be signed in to change notification settings - Fork 62
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 cdk tests when new dependencies are shipped to npm. #2107
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: d3b5701 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
rtpascual
approved these changes
Oct 11, 2024
ShadowCat567
approved these changes
Oct 14, 2024
vigy02
pushed a commit
that referenced
this pull request
Oct 14, 2024
* Fix cdk tests when new dependencies are shipped to npm. * try this * try this * try this * try this
vigy02
added a commit
that referenced
this pull request
Oct 31, 2024
…nstruct (#2087) * fix: clearing the .amplify/generated/env/ before synthesis * fix: clearing the .amplify/generated/env/ before synthesis * fix: clearing the .amplify/generated/env/ before synthesis * fix: clearing the .amplify/generated/env/ before synthesis * fix: clearing the .amplify/generated/env/ before synthesis * fix: clearing the .amplify/generated/env/ before synthesis * chore: add changeset * fix: clearing the .amplify/generated/env/ before synthesis * fix: clearing the .amplify/generated/env/ before synthesis * fix: clearing the .amplify/generated/env/ before synthesis * fix: Clear generated env directory before shim generation * fix: Clear generated env directory before shim generation * fix: Clear generated env directory before shim generation * fix: Clear generated env directory before shim generation * chore: add changeset * fix: Clear generated env directory before shim generation * fix: Clear generated env directory before shim generation * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * feat: adding custom lambda function trigger for email * cleanup * chore: removed unwanted changesets * chore: preparing for merge * chore: preparing for merge * chore: preparing for merge * feat: added a functionality to translate auth-props for custom fucntion email * chore: added changeset * chore: added new API * feat: added a functionality to translate auth-props for custom fucntion email * feat: added a test case to cover custom function in backend-auth * feat: added a test case to cover custom function in backend-auth * feat: added a test case to cover custom function in backend-auth * feat: added a test case to cover custom function in backend-auth * feat: added a test case to cover custom function in backend-auth * feat: narrowed down the permission by updating the conditions * Refactored the code * Refactored the code * added a test case for checking lambdaTrigger={} empty condition * added a test case for checking lambdaTrigger={} empty condition * Merge Branch * Merge Branch * Merge Branch * Merge Branch * Merge Branch * Merge Branch * Merge Branch * Merge Branch * Merge Branch * Merge Branch * fixed the code to use addTrigger instead of manually setting up permissions * added KMS Key for customEmailSender * changed KMS key to not read-only * changed the test case to include lambdaArn * add a test case validation for KMS key * fixed the code to use addTrigger instead of manually setting up permissions * added KMS Key for customEmailSender * changed KMS key to not read-only * changed the test case to include lambdaArn * add a test case validation for KMS key * detect transform errors with multiple errors (#2102) * detect transform errors with multiple errors * new method of getting multiple transform errors * Add minify option to defineFunction (#2093) * Add minify option to defineFunction * Add unit tests and e2e tests when set minify option to false * Add changeset * Update API.md * add bundling options * Update .changeset/pink-rockets-dance.md * use optional chaining * include funcNoMinify into function.ts --------- Co-authored-by: Kamil Sobol <[email protected]> * upgrade constructs (#2103) * Remove deprecated messages field from event (#2106) * detect generic CFN stack creation errors (#2108) * Fix cdk tests when new dependencies are shipped to npm. (#2107) * Fix cdk tests when new dependencies are shipped to npm. * try this * try this * try this * try this * API changes * Update API changes * Added kmsKeyArn for custom user KMS keys * chore: added changesets and updated API's * chore: added changesets * Added integration tests for customEmailSender * updated the API files to reflect master * feat: added customSenderEmail with types and added exceptions to eslint dict * chore: Updated API * chore: Updated API * chore: updated API * Delete packages/ai-constructs/API.md * chore: Updated API * chore: delete unused file * chore: update changeset * chore: update changeset * chore: Updated API and changeSets * chore: Updated the API from main * API updates to resolve conflicting naming * Updated the types in backend-auth * chore: Updated changesets * Added custom Email handler function and refactored the types of auth-construct * chore: updated API --------- Co-authored-by: Roshane Pascual <[email protected]> Co-authored-by: MURAKAMI Masahiko <[email protected]> Co-authored-by: Kamil Sobol <[email protected]> Co-authored-by: Kamil Sobol <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Follow up on #2103 .
Constructs shipped once again and updating it is not sustainable.
Changes
Changes in tests to assure that we're using same version across the board.
Validation
this PR checks.
Checklist
run-e2e
label set.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.