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
There are some key concerns with #6 and its accompanying RFC #122. Namely, it does not totally solve the issue that it claims to solve. Further, it creates issues for users hoping to use the library from a limited environment like Lambda, which has a strict upload size limit.
The proposal is to create a limited number of AWS CDK packages, published by grouping L2 constructs under the categories they're listed under on the AWS Console (or another naming convention that we agree on). The L1 constructs will be moved into a singular package along with all other CloudFormation utilities. The core utilities will then be abstracted to a separate core package that can be consumed independent of the CDK (for GitHub Actions for instance).
Progress
Tracking Issue Created
RFC PR Created
Core Team Member Assigned
Initial Approval / Final Comment Period
Ready For Implementation
implementation issue 1
Resolved
The text was updated successfully, but these errors were encountered:
Description
There are some key concerns with #6 and its accompanying RFC #122. Namely, it does not totally solve the issue that it claims to solve. Further, it creates issues for users hoping to use the library from a limited environment like Lambda, which has a strict upload size limit.
The proposal is to create a limited number of AWS CDK packages, published by grouping L2 constructs under the categories they're listed under on the AWS Console (or another naming convention that we agree on). The L1 constructs will be moved into a singular package along with all other CloudFormation utilities. The core utilities will then be abstracted to a separate core package that can be consumed independent of the CDK (for GitHub Actions for instance).
Progress
The text was updated successfully, but these errors were encountered: