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

Kinesis Data Firehose Delivery Stream L2 #340

Closed
9 of 11 tasks
BenChaimberg opened this issue Jun 25, 2021 · 2 comments
Closed
9 of 11 tasks

Kinesis Data Firehose Delivery Stream L2 #340

BenChaimberg opened this issue Jun 25, 2021 · 2 comments
Assignees
Labels
bar-raiser/assigned l2-request request for new L2 construct management/tracking status/done Implementation complete

Comments

@BenChaimberg
Copy link
Contributor

BenChaimberg commented Jun 25, 2021

Description

Support Firehose Delivery Stream as an L2 construct in the framework library.

The aws-kinesisfirehose construct library allows you to create Amazon Kinesis Data Firehose delivery streams and destinations with just a few lines of code. As with most construct libraries, you can also easily define permissions and metrics using a simple API.

Roles

Role User
Author(s) @madeline-k @otaviomacedo @BenChaimberg
API Bar Raiser @rix0rrr

See RFC Process for details

Workflow

  • 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 api-approved applied 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.

@eladb
Copy link
Contributor

eladb commented Jul 7, 2021

@madeline-k @otaviomacedo @BenChaimberg I've updated this issue according to the new RFC process template. Please take a look at the new process description.

Can you also please take a look at the updated RFC template and align your RFC to it (should be quite similar).

@rix0rrr I've assigned you as the API Bar Raiser for this RFC. Your job is to approve the public API described in the RFC. Once approved, please slap an "api-approved" label to the RFC PR.

@BenChaimberg BenChaimberg added status/final-comment-period Pending final approval and removed status/review Proposal pending review/revision labels Jul 8, 2021
@BenChaimberg BenChaimberg added status/approved Ready for implementation and removed status/final-comment-period Pending final approval labels Jul 20, 2021
@BenChaimberg
Copy link
Contributor Author

Implementation tracked in aws/aws-cdk milestone 16

@BenChaimberg BenChaimberg added status/implementing RFC is being implemented and removed status/approved Ready for implementation labels Jul 21, 2021
@otaviomacedo otaviomacedo removed their assignment Nov 5, 2021
@evgenyka evgenyka added l2-request request for new L2 construct bar-raiser/assigned labels Aug 10, 2023
@mrgrain mrgrain added status/done Implementation complete and removed status/implementing RFC is being implemented labels Oct 13, 2023
@mrgrain mrgrain closed this as completed Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bar-raiser/assigned l2-request request for new L2 construct management/tracking status/done Implementation complete
Projects
None yet
Development

No branches or pull requests

6 participants