-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Increased limit for key-value pairs in input_transformer argument of aws_cloudwatch_event_target #19775
Comments
github-actions
bot
added
the
needs-triage
Waiting for first response or review from a maintainer.
label
Jun 11, 2021
anGie44
added
service/cloudwatchevents
and removed
needs-triage
Waiting for first response or review from a maintainer.
labels
Jun 11, 2021
anGie44
added
the
waiting-response
Maintainers are waiting on response from community or contributor.
label
Jun 11, 2021
Hi!
Yeah that was the one! I will upgrade my dependencies then!
Thanks!
On 11 Jun 2021, at 19:04, angie pinilla ***@***.***> wrote:
Hi @rsotogar <https://github.com/rsotogar> 👋 Our you referring to the limit set on input_paths? Our latest release of the provider (v3.45.0) now sets the limit fo input_paths to 100 key/value pairs (per the AWS API specs).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#19775 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOEEBZMDQ7LMRMN5XLI3R5LTSI6YZANCNFSM46RC4CXQ>.
Ramon Soto, PhD.
|
Sounds good! Closing this as fixed 👍 |
anGie44
removed
the
waiting-response
Maintainers are waiting on response from community or contributor.
label
Jun 11, 2021
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, it'd be really useful for me to increase the limit of selected key-value pairs in this argument. Using only 10 really limits my application since some of my input records contain dozens of fields. Thanks!
The text was updated successfully, but these errors were encountered: