Skip to content
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

Closed
rsotogar opened this issue Jun 11, 2021 · 4 comments

Comments

@rsotogar
Copy link

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!

@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Jun 11, 2021
@anGie44 anGie44 added service/cloudwatchevents and removed needs-triage Waiting for first response or review from a maintainer. labels Jun 11, 2021
@anGie44
Copy link
Contributor

anGie44 commented Jun 11, 2021

Hi @rsotogar 👋 Are you referring to the limit set on input_paths? A similar issue was reported this week and fixed (#19698). 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).

@anGie44 anGie44 added the waiting-response Maintainers are waiting on response from community or contributor. label Jun 11, 2021
@rsotogar
Copy link
Author

rsotogar commented Jun 11, 2021 via email

@anGie44
Copy link
Contributor

anGie44 commented Jun 11, 2021

Sounds good! Closing this as fixed 👍

@anGie44 anGie44 closed this as completed Jun 11, 2021
@anGie44 anGie44 removed the waiting-response Maintainers are waiting on response from community or contributor. label Jun 11, 2021
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants