[appmesh] Implement missing Route Match features

[dfezzie]

There are fields that are currently not exposed in the App Mesh Route match spec. To enable different use cases, we need to allow customers to configure them for each route protocol.

Use Case

One of the most powerful features that this exposes is header based routing, but there are other use cases that customers can take advantage of. We also need to expose the priority field on the Route to disambiguate when multiple routes may match the same request

Proposed Solution

Here is an example:

router.addRoute('test-http-route', {
  routeSpec: appmesh.RouteSpec.http({
    match: {
      prefixPath: '/node',
      headers: [
        {
          match: appmesh.MatchCriteria.exact,
          name: 'foo',
          invert: false,
        },
      ],
      ...
    }
    ...
    weightedTargets: [
      {
         virtualNode: node,
      },
    ],
  }),
});

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.