-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug/Enhancement]: appmesh_route needs support for port matching #27698
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
In addition aws_appmesh_virtual_gateway only supports a single listener (even though #14169 states this has been implemented). Also aws_appmesh_gateway_route would also need to support the matching on port and the target port setting). |
This functionality has been released in v4.51.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
app mesh routes seem to require setting port matching on the route. I actually can't get it to work at all without doing this, which means that this resource is currently useless?
Affected Resource(s) and/or Data Source(s)
appmesh_route
Potential Terraform Configuration
References
error when adding router listeners:
port config from gui:
Would you like to implement a fix?
No response
The text was updated successfully, but these errors were encountered: