Event Pattern Matching

[rubenkaiser]

Event Pattern Matching

[rubenkaiser]

Hi, you're welcome. Had a quick look on my mobile and you are right. The AWS docs also state that your config is valid. The check you are referring to (.includes) should be replaced and check the type first (array or object). I will provide a fix in the coming days and keep you posted.

[rubenkaiser]

Hi, just published a beta release with a quick fix to see if it will work in your project. In this case the plugin only handles detail patterns one level deeper than previously. If this works I'll update the plugin later with a more robust solution that can handle all kinds of objects and depts.

https://www.npmjs.com/package/serverless-offline-aws-eventbridge/v/1.4.0-beta.1

[nason]

Hi @rubenkaiser thanks for the quick response. The beta version does work with the sample I posted!

Some of our other subscriptions are more nested, and those show the same issue. For example:

{
  source: ['graph'],
  'detail-type': ['update'],
  detail: {
    trigger: {
      // @ts-ignore: this is a valid pattern
      name: ['company'],

      event: {
        data: {
          new: {
            status: ['archived'],
          },
        },
      },
    },
  },
},

Please let me know if there is any way I can help!

[rubenkaiser]

Hi @nason. Good to see that the first test worked for you. I've just release a new beta version in which I had a go to fixing the more nested subscriptions. In this case I decided to flatten the subscription pattern, as well as the event detail. After that I've check if the event has the right properties.

You can see the solution in this PR (it also has some husky stuff, but you can ignore that)
#13

I think this is a nice generic solution that works very well. Can you check it in your setup?

https://www.npmjs.com/package/serverless-offline-aws-eventbridge/v/1.4.0-beta.2

[rubenkaiser]

Fixed by #13