[AWS SDK for Go Migration] App Mesh Service

[breathingdust]

Description

To align with the dates described on #32976 the App Mesh Service requires migration to rely fully on AWS SDK for Go v2. This change should be mechanical in nature and not introduce any behavior changes.

The maintainer team will be working on these migrations but as always, help from the community is always appreciated. We would require passing acceptance tests for the entire set of resources being migrated. (We will also validate on review)

For further information about the migration, please see the parent issue #32976.

Resources In Scope for Migration

"aws_appmesh_gateway_route"
"aws_appmesh_mesh"
"aws_appmesh_route"
"aws_appmesh_virtual_gateway"
"aws_appmesh_virtual_node"
"aws_appmesh_virtual_router"
"aws_appmesh_virtual_service"

Data Sources In Scope for Migration

"aws_appmesh_gateway_route"
"aws_appmesh_mesh"
"aws_appmesh_route"
"aws_appmesh_virtual_gateway"
"aws_appmesh_virtual_node"
"aws_appmesh_virtual_router"
"aws_appmesh_virtual_service"

References

• 32976

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.