-
Notifications
You must be signed in to change notification settings - Fork 0
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
Support CDK v2.x #1
Comments
I faced this issue before. Is it fixed in the latest |
It does not look like so. |
As far as I tested, it was fixed since |
|
- `@aws-cdk/core` and `@aws-cdk/aws-lambda` are replaced with `constructs` and `aws-cdk-lib`. - Outdated packages are also updated. issue #1
- `cdk.*` classes are imported from new modules, - `Construct` is from `constructs`. - `AssetStaging`, `FileSystem`, and `DockerImage` are from `aws-cdk-lib`. - `aws_lambda` is imported as `lambda` from `aws-cdk-lib`. issue #1
- The example project is re-created with the CDK v2. And `cdk-python-library-layer` is replaced with `cdk2-python-library-layer`. issue #1
- `README.md` and `README_ja.md` are adapted for the version 2.x. issue #1
- The version tagged with "v0.1.0-v2" is installed. issue #1
- `README.md` and `README_ja.md` show a link to the v2.x branch. issue #1
Please support CDK v2.x. Maybe in a dedicated branch like
v2.x
.The text was updated successfully, but these errors were encountered: