-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[AWS SDK for Go Migration] Service Catalog Service #36211
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Can we close this issue? We solved it with #36009 |
Closes via #36009. |
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. |
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
To align with the dates described on #32976 the Service Catalog 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
Data Sources In Scope for Migration
References
The text was updated successfully, but these errors were encountered: