Add support tags attribute for aws_appmesh_route resource

[teraken0509]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" comments, they generate extra noise for pull request followers and do not help prioritize the request

Reference #8101

Release note for CHANGELOG:

ENHANCEMENTS:
- resource/aws_appmesh_route: Add `tags` argument.

Output from acceptance testing:

$ make testacc TEST=./aws TESTARGS='-run=TestAccAWSAppmesh/Route'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -parallel 20 -run=TestAccAWSAppmesh/Route -timeout 120m
=== RUN   TestAccAWSAppmesh
=== RUN   TestAccAWSAppmesh/Route
=== RUN   TestAccAWSAppmesh/Route/httpRoute
=== RUN   TestAccAWSAppmesh/Route/tcpRoute
=== RUN   TestAccAWSAppmesh/Route/tags
=== RUN   TestAccAWSAppmesh/VirtualRouter
=== RUN   TestAccAWSAppmesh/VirtualRouter/basic
--- PASS: TestAccAWSAppmesh (234.94s)
    --- PASS: TestAccAWSAppmesh/Route (187.98s)
        --- PASS: TestAccAWSAppmesh/Route/httpRoute (56.43s)
        --- PASS: TestAccAWSAppmesh/Route/tcpRoute (54.72s)
        --- PASS: TestAccAWSAppmesh/Route/tags (76.82s)
    --- PASS: TestAccAWSAppmesh/VirtualRouter (46.97s)
        --- PASS: TestAccAWSAppmesh/VirtualRouter/basic (46.97s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	235.057s

[bflad]

LGTM, thanks @kterada0509 🚀

--- PASS: TestAccAWSAppmesh (149.77s)

[bflad]

This has been released in version 2.18.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 for triage. Thanks!

[ghost]

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.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!