You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CDK team has shell script that reads CLIENT_PACKAGE_NAMES_MAP.ts to generate SDK v2 to v3 mapping. As mentioned in issue comment, it transforms MemoryDB from CLIENT_NAMES.ts to memory-db here. Per MemoryDBClient, the service name is memorydb (not memory-db) with package name as @aws-sdk/client-memorydb.
Steps to reproduce
N/A
Observed behavior
SDK v2-to-v3 mapping is incorrect for Memory DB service. It is memory-db.
Expected behavior
SDK v2-to-v3 mapping for Memory DB service should be memorydb.
Environment
aws-sdj-js-codemod: latest
Additional context
No response
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.
Self-service
Describe the bug
There is an issue reported in CDK repo by external customer: issue aws/aws-cdk#31755 (comment).
CDK team has shell script that reads CLIENT_PACKAGE_NAMES_MAP.ts to generate SDK v2 to v3 mapping. As mentioned in issue comment, it transforms MemoryDB from CLIENT_NAMES.ts to memory-db here. Per MemoryDBClient, the service name is memorydb (not memory-db) with package name as @aws-sdk/client-memorydb.
Steps to reproduce
N/A
Observed behavior
SDK v2-to-v3 mapping is incorrect for Memory DB service. It is
memory-db
.Expected behavior
SDK v2-to-v3 mapping for Memory DB service should be
memorydb
.Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: