[AWS SDK for Go Migration] Verified Access Service

[breathingdust]

Description

To align with the dates described on #32976 the Verified Access 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_verifiedaccess_endpoint"
"aws_verifiedaccess_group"
"aws_verifiedaccess_instance"
"aws_verifiedaccess_instance_logging_configuration"
"aws_verifiedaccess_instance_trust_provider_attachment"
"aws_verifiedaccess_trust_provider"

Data Sources In Scope for Migration

References

• [Provider]: Migration to aws-sdk-go-v2 #32976

[github-actions]

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.

[DanielRieske]

@breathingdust I believe we can close this issue, I double-checked them and all these resources have been created using SDKv2 since the start.

#33297
#33459
#33734
#33864
#34156

[johnsonaj]

Verified Access service is already on AWS SDKv2

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.