-
Notifications
You must be signed in to change notification settings - Fork 157
feat: Pipes log configuration support #125
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: Pipes log configuration support #125
Conversation
@magreenbaum Please assign a reviewer once you are done. It already looks very good to me. Thanks! |
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.
LGTM
## [3.5.0](v3.4.0...v3.5.0) (2024-06-13) ### Features * Pipes log configuration support ([#125](#125)) ([9e21611](9e21611))
This PR is included in version 3.5.0 🎉 |
I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Support
aws_pipes_pipe
log_configuration
.Added
force_destroy
toaws_cloudwatch_event_target
andaws_cloudwatch_event_rule
.Updated api-gateway module due to breaking major version changes.
Motivation and Context
hashicorp/terraform-provider-aws#37135
hashicorp/terraform-provider-aws#34905
hashicorp/terraform-provider-aws#37130
Breaking Changes
No.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request