![]() TheĮxception is that when two or more related experimental modules depend on each other, theyįor stable modules to which new functionality is being added, new APIs (whether entirely You can upgradeĪws-cdk-lib or the experimental module whenever you want. Once a module has been designated stable and incorporated intoĪws-cdk-lib, new APIs are added using the "BetaN" conventionĪ new version of each experimental module is released with every release of the AWS CDK.įor the most part, however, they needn't be kept in sync. Writing has only L1 constructs, they first appear in a module Then, they move toĪws-cdk-lib when we feel that the new constructs meet the fundamental More L2 constructs for Amazon AppFlow, which at this Stability is specified at the service level. Main Construct Library to adhere to strict semantic versioning. Move into aws-cdk-lib after being designated stable, permitting the That they're compatible with, also with an alpha suffix. The semantic version number matches the first version of the AWS Construct Library Instead, they're distributed as individual packages.Įxperimental packages are named with an alpha suffix and a semantic ![]() ![]() L1 (CfnXXXX) constructs, which represent the exact resources available in AWS CloudFormation, areĪlways considered stable and so are included in aws-cdk-lib.Įxperimental modules, where we're still working with the community to develop new L2 or 元 constructs, are not included inĪws-cdk-lib. Single-package approach also means that you don't have to synchronize the versions of the Need to install additional packages for the individual AWS services they use. AWS CDK v2 consolidates the stable parts of the AWS Construct Library, including theĬore library, into a single package, aws-cdk-lib. ![]()
0 Comments
Leave a Reply. |