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.

Sign up for GitHub

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

Jump to bottom

Status of Kinesis Firehose module #5626

Closed
1 of 2 tasks
lukehedger opened this issue Jan 3, 2020 · 3 comments
Closed
1 of 2 tasks

Status of Kinesis Firehose module #5626

lukehedger opened this issue Jan 3, 2020 · 3 comments
Assignees
@iliapolo
Labels
@aws-cdk/aws-kinesis Related to Amazon Kinesis @aws-cdk/aws-kinesisfirehose Related to Amazon Kinesis Data Firehose effort/large Large work item – several weeks of effort feature-request A feature should be added or improved.

Comments

@lukehedger
Copy link
Contributor

What is the status of the Kinesis Firehose construct - is it being actively worked on or is it planned work? It'd be helpful to have this information to determine whether we can wait for the module to land or to define this part of our infra in another way.

Use Case

Define Kinesis Data Firehose infrastructure using the CDK.

Other

  • 👋 I may be able to implement this feature request
  • ⚠️ This feature might incur a breaking change

This is a 🚀 Feature Request
@lukehedger lukehedger added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels Jan 3, 2020
@SomayaB SomayaB added @aws-cdk/aws-kinesis Related to Amazon Kinesis @aws-cdk/aws-kinesisfirehose Related to Amazon Kinesis Data Firehose labels Jan 6, 2020
@SomayaB SomayaB removed their assignment Jan 28, 2020
@SomayaB
Copy link
Contributor

SomayaB commented Jan 28, 2020 •
edited
Loading

Hi @lukehedger, sorry for the late reply. We are not working on Firehose at the moment but we welcome any contribution.

@SomayaB SomayaB removed the needs-triage This issue or PR still needs to be triaged. label Jan 28, 2020
@skinny85 skinny85 added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. gap effort/large Large work item – several weeks of effort labels Feb 6, 2020
@SomayaB SomayaB added closing-soon This issue will automatically close in 4 days unless further comments are made. and removed response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. closing-soon This issue will automatically close in 4 days unless further comments are made. labels Feb 10, 2020
@SomayaB SomayaB removed the gap label Feb 25, 2020
@skinny85 skinny85 assigned iliapolo and unassigned skinny85 Mar 19, 2020
@lukehedger
Copy link
Contributor Author

This feature is now being tracked in #7536 - add a 👍 there if you'd like to see it implemented!

@iliapolo
Copy link
Contributor

Closing in favor of the tracking issue mentioned here: #7536

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iliapolo iliapolo

Labels
@aws-cdk/aws-kinesis Related to Amazon Kinesis @aws-cdk/aws-kinesisfirehose Related to Amazon Kinesis Data Firehose effort/large Large work item – several weeks of effort feature-request A feature should be added or improved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@skinny85 @iliapolo @lukehedger @SomayaB