-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Meta Issue: Migrate to upstream awslabs/aws-sdk-go #1488
Comments
@catsby I'm trying to take a shot at converting the instance resource but hitting errors like
Could you help point me in the right direction? |
Figured it out... it helps if I use the correct methods 😄 |
@catsby just in case you were waiting for me on the instance conversion, I moved on to route53 (which you got covered) and haven't come back to instance yet, feel free to bring that over. Thanks again for all this! |
No worries, I'm doing Instance today and then we'll be done! |
Everything is merged! |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
This is a meta issue to track our migration of AWS resources to the upstream version of
aws-sdk-go
at https://github.com/awslabs/aws-sdk-go.If anyone would like to contribute, see my previous PRs (linked below) for examples of the general work to be done in each PR. To aid us here, there are upstream versions of
tags.go
andstructure.go
, with the_sdk
prefix. In them are theawslabs
version of the methods contained in the originals, sotagsToMap
becomestagsToMapSDK
, etc.Questions?
Missing something?
Ask and I'm here to help 😄
The text was updated successfully, but these errors were encountered: