Differences

This shows you the differences between two versions of the page.

--- bloglike:2021-07 [2021/07/21 03:36] – final touches and we're done. case closed. I hope. stybla
+++ bloglike:2021-07 [2021/07/21 09:20] – use code block instead of quote stybla
@@ Line 30: / Line 30: @@
 I guess all of this could've been done much faster and less painful with a simple Lambda function, but then you have code to maintain and deploy.
-Couple more things. Beware of this [[https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/351#issue-552650814|bug]]. Over and out.
+Couple more things. Beware of this [[https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/351#issue-552650814|bug]].
 > Note: CloudWatch Events currently supports a maximum of 10 variables in input path maps. To extract more than 10 variables, pass the entire event to an AWS Lambda function for parsing.
-Well, I able to parse 13 variables. Lucky me, I guess. 8-) As I've said, use Lambda function, if you can. Yeah, anything but CloudWatch Logs.
+Well, I able to parse 13 variables. Lucky me, I guess. 8-) Or maybe not, because when I've tried to put this into terraform, then:
+<code>
+Error: expected number of items in input_transformer.0.input_paths to be less than or equal to 10, got 16
+</code>
+To that I say, bollocks! It works no-problem from the console, so why would you ...?! Bloody hell! As I've said, use Lambda function, if you can. Yeah, anything but CloudWatch Log
 You can filter which events get processed like so: