Okay, I’ve been struggling with what I think may be a bug in the rule_event resource and thought I’d surface it here before I head over to Github and submit it as an issue. I’m still learning my way around the Jets codebase and don’t think I’m quite in a place where I’d be able to submit a PR but if this does indeed look like a bug and you’d like to point me in the right direction I’d be happy to dig in and see if I can submit a PR. In the meantime, here’s what I’m seeing.
My “rule_event” call looks like so:
rule_event( description: "Checks for orders", detail_type: ['shopify_order_import'] )
When I attempt a deploy, I receive an error and my cloud formation is rolled back. After digging into a few things, I noticed that “detail_type” is converted to “detail-type” and if I have other attributes in that rule_event call with underscores like “line_items”, they get converted to camelCase as well like “lineItems”. Here’s the exact error message that I’m getting from CloudFormation: https://www.dropbox.com/s/t86mhpsgantv6g2/Screen%20Shot%202021-03-06%20at%206.29.40%20PM.png?dl=0 and here’s a screenshot of a what this rule looks like in Event Bridge: https://www.dropbox.com/s/zvxoc2dkd0qorjl/Screen%20Shot%202021-03-06%20at%206.29.48%20PM.png?dl=0
I should note that the last screenshot I shared was when I took a different approach to applying that rule using this pattern format: https://www.dropbox.com/s/ufrhv6pisfkrjs4/Screen%20Shot%202021-03-06%20at%206.40.08%20PM.png?dl=0 but the outcome did result in some formatting that did not match my rules. Any who, I’m going to try a different approach and try to use the full “resource” approach and see if that will at least get me operational but would love any insight you might have @tung.
Please let me know if I can provide any additional information to help troubleshoot. Thanks!