-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[Enhancement]: EventBridge Pipes #28153
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
I've picked up |
FTR: Anybody interested to give a shot to AWS EventBridge Pipes may use temporary resource "aws_cloudformation_stack" "cloudformation_stack" {
name = "CostAnomalyUpdates"
parameters = {
RoleArn = aws_iam_role.cost_anomaly_updates_event_bridges_role.arn
SourceArn = aws_sqs_queue.cost_anomaly_updates.arn
TargetArn = aws_cloudwatch_log_group.cloudwatch-group.arn
}
template_body = jsonencode({
"Parameters" : {
"SourceArn" : {
"Type" : "String",
},
"TargetArn" : {
"Type" : "String",
},
"RoleArn" : {
"Type" : "String"
}
},
"Resources" : {
"CopyPipe" : {
"Type" : "AWS::Pipes::Pipe",
"Properties" : {
"Name" : "CostAnomalyUpdates-SQS-to-CW",
"RoleArn" : { "Ref" : "RoleArn" }
"Source" : { "Ref" : "SourceArn" },
"Target" : { "Ref" : "TargetArn" },
}
}
}
})
} |
Apologies, this is still in progress... Some of the sources and targets have invisible, un-documented default parameter values, which has been difficult to reconcile with Terraform's diffs under some combinations of resource updates. I'm slowly inching towards solving the edge cases, but it may yet be some time before this is complete. |
The best docs I found are on the CLI's documentation: |
@roberth-k Your changes were merged into main a couple of months ago; did this make it to a new terraform version? ETA: I see the pipes module is part of awscc provider, not aws as I was expecting. May I have an example for creating a Pipe with an active_mq source and bus target? I don't see where to put the ARN of the active mq, I only see the basic_auth and queue name parameters. |
Looks like this issue did not get closed with the PR merge. Closing it out as the resource in the pr covers the request. |
@roberth-k was this left open intentionally? I want to make sure I am only closing the issue if it’s actually completed. |
Hi @brittandeyoung -- #30538 is a partial implementation, so this issue should remain open. |
Working with @roberth-k on filling out the parameters etc :) |
Working through the tests now! Hopefully shouldn't be too much longer :) |
I've got a PR open, if you give it thumbs up, it'll help get prioritised #31607 (comment) |
This functionality has been released in v5.6.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Please add support for EventBridge Pipes -- see https://aws.amazon.com/eventbridge/pipes/
Affected Resource(s) and/or Data Source(s)
No response
Potential Terraform Configuration
No response
References
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: