-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
aws-events-targets: KinesisFirehoseStream not accepting IDeliveryStream for imported DeliveryStream #25451
Comments
I believe this is because I guess we probably need to allow KinesisFirehoseStream to accept the interface instead.
|
Thank you for the insight, I am using JS (not TS) so did not have any type hints. Is there a prescribed way to get a |
Assuming you've created a deliverystream like so:
You can access the
|
Sorry, you're importing it. If your |
…eam for imported deliverystream (#30189) ### Issue # (if applicable) Closes #25451 ### Reason for this change Current events targets implementation only support L1 Delivery Stream as the input. We should support L2 IDeliveryStream as well for imported kinesis firehose stream. ### Description of changes Add a V2 class to support kinesis firehose stream. ### Description of how you validated changes New tests and existing tests pass. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
…eam for imported deliverystream (aws#30189) ### Issue # (if applicable) Closes aws#25451 ### Reason for this change Current events targets implementation only support L1 Delivery Stream as the input. We should support L2 IDeliveryStream as well for imported kinesis firehose stream. ### Description of changes Add a V2 class to support kinesis firehose stream. ### Description of how you validated changes New tests and existing tests pass. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Okay so I'm really struggling with a mismatch here: I'm creating a DeliveryStream
Then I create a rule and try to add the DeliveryStream as a target. No matter what I try here I can't seem to resolve this. I can't use the L2 DeliveryStream construct because I need access to a lot of the configuration parameters as above.
In your changes @pahud @atanaspam @GavinZZ did you mean to stop supporting CfnDeliveryStream as a type for this method. If so, how do I reconcile a CfnDeliveryStream to match an IDeliveryStream? |
Describe the bug
When trying to add a KinesisFirehoseStream target to an event Rule, an error is thrown out of the
aws-iam
module.Expected Behavior
CDK will successfully create an event rule with a target of an existing Kinesis Firehose stream.
Current Behavior
An error is thrown:
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.77.0 (build 06a0b19)
Framework Version
No response
Node.js Version
v16.14.2
OS
Ubuntu
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: