-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Migrate to AWS SDKv2 #770
Closed
Comments
This was referenced Oct 16, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Oct 20, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Oct 20, 2024
…shboard, cloudWatch logGroup, codeDeploy Application, dynamodb to awsSDKv2 gruntwork-io#770
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Oct 20, 2024
… location, dataSync task to awsSDKv2 gruntwork-io#770
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Oct 26, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Oct 26, 2024
…shboard, cloudWatch logGroup, codeDeploy Application, dynamodb to awsSDKv2 gruntwork-io#770
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Oct 26, 2024
… location, dataSync task to awsSDKv2 gruntwork-io#770
james03160927
pushed a commit
that referenced
this issue
Oct 28, 2024
* change port access_analyzer, acm, acmpca, ami, API GWv1 & API GWv2 to awsSDKv2 #770 * change port backup vault, cloudTrail, cloudWatch alarm, cloudWatch dashboard, cloudWatch logGroup, codeDeploy Application, dynamodb to awsSDKv2 #770 * change port appRunner, ASG, config recorder, config service, dataSync location, dataSync task to awsSDKv2 #770
5 tasks
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Oct 31, 2024
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Oct 31, 2024
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Oct 31, 2024
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Nov 1, 2024
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Nov 3, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Nov 6, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Nov 9, 2024
…ey pair, ec2 placement group, kinesis firehose, kinesis stream, kms customer key, lambda layer, lambda, macie to awsSDKv2 gruntwork-io#770
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Nov 9, 2024
…ey pair, ec2 placement group, kinesis firehose, kinesis stream, kms customer key, lambda layer, lambda, macie to awsSDKv2 gruntwork-io#770
5 tasks
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 5, 2024
james03160927
pushed a commit
that referenced
this issue
Dec 6, 2024
* register missing resource - TGW Peering Attachment * change port transit-gateway-peering-attachment to awsSDKv2 #770
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 6, 2024
gruntwork-io#770), we should remove any remaining v1 calls.
9 tasks
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 11, 2024
gruntwork-io#770), we should remove any remaining v1 calls.
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 15, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 15, 2024
james03160927
pushed a commit
that referenced
this issue
Dec 17, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 17, 2024
gruntwork-io#770), we should remove any remaining v1 calls.
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 17, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 17, 2024
Re-opening this as there a couple more PRs to complete. |
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 20, 2024
gruntwork-io#770), we should remove any remaining v1 calls.
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 20, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 20, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 21, 2024
gruntwork-io#770), we should remove any remaining v1 calls.
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 21, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 21, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 21, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 21, 2024
wakeful
added a commit
to wakeful/cloud-nuke
that referenced
this issue
Dec 21, 2024
james03160927
pushed a commit
that referenced
this issue
Dec 24, 2024
#770), we should remove any remaining v1 calls. (#804) * after completing all work related to the AWS SDK v2 resource migration (#770), we should remove any remaining v1 calls. * clean up `util` pkg, rm `awsgo` pkg alias, part of AWS SDK v2 resource migration (#770). * rm AWS SDK v2 migration report. * rm `awserr` pkg usage, part of AWS SDK v2 resource migration (#770). * rm unused `IsUsingV2` function, part of AWS SDK v2 resource migration (#770). * rename `InitV2` function to `Init`, part of AWS SDK v2 resource migration (#770).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The AWS SDK v1 is officially deprecated (end-of-support is July 31, 2025). We need to migrate code to v2 before it ends the support for this.
The text was updated successfully, but these errors were encountered: