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

Add validator for aws_cloudwatch_event_target input_transformer.input_paths maximum size #15653

Closed
gdavison opened this issue Oct 14, 2020 · 3 comments · Fixed by #15669
Closed
Labels
documentation Introduces or discusses updates to documentation. service/cloudwatch Issues and PRs that pertain to the cloudwatch service.
Milestone

Comments

@gdavison
Copy link
Contributor

gdavison commented Oct 14, 2020

According to https://docs.aws.amazon.com/eventbridge/latest/APIReference/API_InputTransformer.html#API_InputTransformer_Contents, the input_transformer input_paths map can have a maximum of 10 entries. There is no validation of this maximum, nor is this documented in Terraform documentation.

Affected Resource

  • aws_cloudwatch_event_target

References

@ghost ghost added service/cloudwatchevents service/cloudwatch Issues and PRs that pertain to the cloudwatch service. labels Oct 14, 2020
@gdavison gdavison removed the service/cloudwatch Issues and PRs that pertain to the cloudwatch service. label Oct 14, 2020
@ghost ghost added the service/cloudwatch Issues and PRs that pertain to the cloudwatch service. label Oct 14, 2020
@gdavison gdavison added the documentation Introduces or discusses updates to documentation. label Oct 14, 2020
@philnichol
Copy link
Contributor

@gdavison mind if I have a crack at this one?

@ghost
Copy link

ghost commented Oct 22, 2020

This has been released in version 3.12.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 for triage. Thanks!

@ghost
Copy link

ghost commented Nov 20, 2020

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Nov 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Introduces or discusses updates to documentation. service/cloudwatch Issues and PRs that pertain to the cloudwatch service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants