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
I read about how alpha modules work in this blogpost
We can read here that After an alpha module stabilizes, it will be moved to aws-cdk-lib and have a guaranteed backwards compatibility within the AWS CDK major version.
I'm building a cloudfront distro which will use some edge lamdbas, and I'm confused about the fact that the EdgeFunction actually sits in the stable aws_cloudfront module, but in a package named experimental.
So based on the blog post, the function should be stable since it exists in aws-cdk-lib, but the experimental name suggests otherwise.
Can someone help me understand the current state of EdgeFunction?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I read about how alpha modules work in this blogpost
We can read here that
After an alpha module stabilizes, it will be moved to aws-cdk-lib and have a guaranteed backwards compatibility within the AWS CDK major version.
I'm building a cloudfront distro which will use some edge lamdbas, and I'm confused about the fact that the EdgeFunction actually sits in the stable aws_cloudfront module, but in a package named experimental.
So based on the blog post, the function should be stable since it exists in aws-cdk-lib, but the experimental name suggests otherwise.
Can someone help me understand the current state of EdgeFunction?
Beta Was this translation helpful? Give feedback.
All reactions