Skip to content
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

Complete Construct Model #611

Open
awsmjs opened this issue Jan 18, 2024 · 3 comments
Open

Complete Construct Model #611

awsmjs opened this issue Jan 18, 2024 · 3 comments

Comments

@awsmjs
Copy link
Contributor

awsmjs commented Jan 18, 2024

Description

It’s clear that constructs are imperative to the CDK experience. We repeatedly hear from CDK builders that the most important improvement that the CDK can make for its construct experience would be to provide greater service coverage. Because of this, the CDK team is investigating how we can provide more comprehensive AWS service coverage. In the past, the CDK has relied on community and in-house authored constructs to address construct demand. In the future, our goal is to bring CDK builders a complete and consistent construct model through largely autogenerated means. This model would provide builders with Day 1 support of AWS services--the moment services are launched--complete with the features that builders love in their L2s. As we are investigating this effort, it’s possible that there will be gradual rollouts for us to realize this goal. If you have any feedback or comments on this, we would highly appreciate you sharing them as a comment within this RFC.

@alecl
Copy link

alecl commented Feb 29, 2024

It would be great to prioritize the EventBridge Scheduler L2 targets moving out of alpha. It's tough to justify moving to an API that may have vastly breaking changes (what Alpha implies) happen at any time.

In particular, the Lambda Invoke one is the highest value for my groups and likely many others.

https://github.com/aws/aws-cdk/blob/main/packages/%40aws-cdk/aws-scheduler-targets-alpha/lib/lambda-invoke.ts

@gshpychka
Copy link

To be honest, it's not clear how you could achieve L2s via autogenerated means - could you give an example? As far as I understand, the purpose of L2 Constructs is to provide developers with opinionated abstractions - someone in the loop must be injecting these opinions.

@bdoyle0182
Copy link

bdoyle0182 commented Dec 10, 2024

@gshpychka an LLM with a baseline ruleset / design principles made by aws / the community to follow could make those opinionated decisions :)

AWS / the community can review and validate the principles were followed in the generation, which is still a significantly decrease in human development effort to add new constructs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants