Moved RequiredWith from wrong attribute on an appmesh route

[bjernie]

If you create an aws_appmesh_route and provide a spec.0.grpc_route.0.match.service_name it gives an error that you also need to specify a spec.0.grpc_route.0.match.method_name when it is actually the other way around.

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[jar-b]

LGTM 🎉

plan now returns the proper error message:

│ Error: Missing required argument
│
│   with aws_appmesh_route.test,
│   on main.tf line 58, in resource "aws_appmesh_route" "test":
│   58:       match {
│
│ "spec.0.grpc_route.0.match.0.method_name": all of `spec.0.grpc_route.0.match.0.method_name,spec.0.grpc_route.0.match.0.service_name` must be specified

GRPC Route Match Docs: https://docs.aws.amazon.com/app-mesh/latest/APIReference/API_GrpcRouteMatch.html

[jar-b]

Thanks for your contribution, @bjernie! 👏

[github-actions]

This functionality has been released in v4.55.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!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.