Refactor for AWS SDK Upgrade from v2 to v3 #191
Conversation
This file contains hidden or 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
- Refactored AWS SDK imports to use v3 clients and commands in DynamoDBConnectionManager, DynamoDBEventProcessor, DynamoDBEventStore, DynamoDBRangeSubscriptionManager, DynamoDBSubscriptionManager, and RedisConnectionManager. - Updated Babel configuration to include new plugins for class properties and static blocks. - Enhanced Jest configuration for better compatibility with TypeScript and AWS SDK v3. - Removed deprecated aws-sdk dependency from package.json and replaced it with specific AWS SDK v3 packages. - Updated tests to reflect changes in the AWS SDK usage and ensure compatibility with the new structure.
- Changed package name from 'aws-lambda-graphql' to '@the_pixelport/aws-lambda-graphql'. - Updated version from '1.0.0-alpha.24' to '1.0.1'. - Adjusted DynamoDB client initialization to include marshalling options for class instances. - Updated references in package-lock.json and yarn.lock to reflect the new package name and version.
- Updated DynamoDB client initialization to ensure proper marshalling options are applied, including `removeUndefinedValues`. - Added console warnings for potential marshalling issues when using `DynamoDBDocumentClient` directly. - Introduced debug logging in various classes to aid in tracing connection and endpoint handling. - Updated package version from 1.0.1 to 1.0.4 in package.json and package-lock.json.
…gging - Added debug logging functionality to DynamoDBConnectionManager, RedisConnectionManager, and Server classes to improve traceability. - Removed unnecessary console logs in extractEndpointFromEvent function. - Introduced a debug option in connection manager and server configurations to enable or disable logging.
- Documented the update of AWS SDK to V3 and changes to Babel configuration by [@pixelport](https://github.com/pixelport), see [michalkvasnicak#152](michalkvasnicak#152).
- Changed the Docker image in the CircleCI config from circleci/node:10.17.0 to cimg/node:22 for improved compatibility and performance.
…ved compatibility
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
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.
In relation to #152, I did a refactoring to upgrade AWS SDK from v2 to v3