-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(kinesisfirehose): add HTTP Endpoint and Datadog destination #33657
base: main
Are you sure you want to change the base?
feat(kinesisfirehose): add HTTP Endpoint and Datadog destination #33657
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(This review is outdated)
This is my first time creating a pull request for this project so any feedback is appreciated. I'm still figuring out the integration tests and have left this in draft while I work on it. |
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
Seemed fairly obvious after a while that an L2 for an HTTP destination should come first. Not sure if this would be the right approach to reuse it for Datadog. |
a5f07dc
to
fb42a8d
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Issue # (if applicable)
Closes #20354 and #15502
Reason for this change
Adding support for HTTP destinations and adding Datadog as an opinionated third-party destination.
Description of changes
Adds support for using Datadog as a delivery destination for Amazon Data Firehose using an L2 HTTP endpoint destination.
Describe any new or updated permissions being added
Nothing.
Description of how you validated changes
Added unit tests. Have not yet added integration tests.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license