[Enhancement]: Allow including execution info for Eventbridge pipe log configuation

[erinkmcd]

Description

Logging support was recently added for eventbridge pipes but there is one option available in the console not yet doable with terraform that I'd love to see.

When setting up logs for an eventbridge pipe with aws_pipes_pipe, for example:

resource "aws_pipes_pipe" "eventbridge-pipe-poc" {
  name     = "eventbridge-pipe-poc"
  role_arn = aws_iam_role.eventbridge_pipe_role.arn
  source   = aws_dynamodb_table.example_table.stream_arn
  target   = module.eventbridge_poc.eventbridge_bus_arn

  log_configuration {
    cloudwatch_logs_log_destination {
      log_group_arn = aws_cloudwatch_log_group.eventbridge_poc_logs.arn
    }
    level = "TRACE"
  }
}

there is not an option to include execution info. In the AWS console, when doing the same thing, there is an option for including exection info (the event payload).

Affected Resource(s) and/or Data Source(s)

aws_pipes_pipe

Potential Terraform Configuration

resource "aws_pipes_pipe" "eventbridge-pipe-poc" {
  name     = "eventbridge-pipe-poc"
  role_arn = aws_iam_role.eventbridge_pipe_role.arn
  source   = aws_dynamodb_table.example_table.stream_arn
  target   = module.eventbridge_poc.eventbridge_bus_arn

  log_configuration {
    cloudwatch_logs_log_destination {
      log_group_arn = aws_cloudwatch_log_group.eventbridge_poc_logs.arn
    }
    include_execution_data = true # this is the part that I'm requesting
    level = "TRACE"
  }
}

References

https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-pipes-logs.html#eb-pipes-logs-execution-data

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.61.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!

[github-actions]

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.