[@aws-cdk/aws-appmesh] AppMesh Stable Changes

AppMesh API Revisions

1. Currently VirtualNode defaults the value of the logging file path parameter to /dev/stdout and is not configurable through the construct’s props. Remove this default and allow customers to configure log location for their specific use case.

2. Change addListeners method signature to not be variadic since VirtualNode only has one listener. Depending on https://github.com/aws/aws-app-mesh-roadmap/issues/120 we may or may not actually want to change this API.

3. Change model so that VirtualService always uses mesh from either router or node and requires mesh property to exist on VirtualRouter and VirtualNode for importing. VirtualNode and VirtualRouter always have to be in same mesh as VirtualService.

---

This is 🐛 Bug Report

[dfezzie]

Ah good call on 2. That is complete 😄

For 3, I think adding that enforcement is valid and would prevent customers misconfiguring their mesh. If it makes sense in terms of CDK API design we could easily implement it.

I agree on the switching the VirtualService to using a union type for the provider. I just took a quick look and we are also doing something similar for VirtualNode service discovery where we accept CloudMap and DNS at the top level. We should change that as well!

[github-actions[bot]]

⚠️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.