aws
L2 Constructs for AWS Event Schemas
Description
Create L2 constructs for AWS Event Schemas. This is tracked in aws-cdk and unblocks schema discovery for event buses.
Roles
| Role | User |
|---|---|
| Proposed by | @rrhodes |
| Author(s) | TBC |
| API Bar Raiser | TBC |
| Stakeholders | TBC |
See RFC Process for details
Workflow
- [x] Tracking issue created (label:
status/proposed) - [ ] API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
- [ ] Kick off meeting
- [ ] RFC pull request submitted (label:
status/review) - [ ] Community reach out (via Slack and/or Twitter)
- [ ] API signed-off (label
status/api-approvedapplied to pull request) - [ ] Final comments period (label:
status/final-comments-period) - [ ] Approved and merged (label:
status/approved) - [ ] Execution plan submitted (label:
status/planning) - [ ] Plan approved and merged (label:
status/implementing) - [ ] Implementation complete (label:
status/done)
Author is responsible to progress the RFC according to this checklist, and apply the relevant labels to this issue so that the RFC table in README gets updated.
Hey @rrhodes 👋
Thank you for submitting this RFC and for your willingness to contribute to the project! Supporting RFC’s from a CDK team member is considered a large effort as it requires a lot of the engineer’s time to support, and would require us to reprioritize other efforts to take it on. At this time, we have prioritized other RFCs that our engineering team will be working on, so we won't be able to move forward with supporting this RFC. On that note, we are working on building out a clearer, more transparent guide to our community contribution processes, which we hope will help provide more clarity for community members when proposing and contributing new features to the project.
In the meantime, if you want to proceed with building out this construct, we recommend self-publishing in either Construct Hub or contributing to the Open Construct Foundation constructs repository. If you need help as you’re building, I recommend reaching out on the cdk.dev slack workspace. You can find more details on publishing your own package in our contributing guide.
As part of our future contribution model updates, we also plan to define a path for community L2 constructs to potentially graduate into the core AWS CDK repository. Thank you again for your proposal, and we look forward to your continued involvement in the community.
Hey @adamjkeller, thanks for your reply. If the CDK team wish to support this RFC at a later time, do let me know and I'll be happy to consider contributing toward this work.