Skip to content
This repository was archived by the owner on Jul 31, 2025. It is now read-only.

Conversation

@aws-sdk-go-automation
Copy link
Contributor

Release v1.19.30 (2019-05-14)

Service Client Updates

  • service/chime: Updates service API and documentation
    • Amazon Chime private bots GA release.
  • service/comprehend: Updates service API, documentation, and paginators
  • service/ec2: Updates service API, documentation, and paginators
    • Pagination support for ec2.DescribeSubnets, ec2.DescribeDhcpOptions
  • service/storagegateway: Updates service API and documentation
    • Add Tags parameter to CreateSnapshot and UpdateSnapshotSchedule APIs, used for creating tags on create for one off snapshots and scheduled snapshots.

@aws-sdk-go-automation aws-sdk-go-automation merged commit 8dcd3d2 into master May 14, 2019
@aws-sdk-go-automation aws-sdk-go-automation deleted the release branch May 14, 2019 18:33
wking added a commit to wking/openshift-installer that referenced this pull request Aug 14, 2019
Sometimes CI leaks untagged subnets.  Because we are allowed to remove
all resources from within a cluster-owned VPC, add a ByVPC walker to
remove these indirectly-owned subnets.

DescribeSubnetsPages has a strange history.  It was initially added in
aws/aws-sdk-go@3664ecc7da (Add initial implementation of pagination,
2015-03-23, aws/aws-sdk-go#247) but was removed in
aws/aws-sdk-go@bad551feb8 (Add support for multi-token pagination
rules, 2015-03-27) as a later step in that same pull request.  It
finally landed in master via aws/aws-sdk-go@52cd98f1ed (Release
v1.19.30, 2019-05-14, aws/aws-sdk-go#2599), but we only vendor
v1.16.14.  It doesn't seem like "zounds of untagged subnets" is a
high-probability thing, so I'm just using the unpaginated
DescribeSubnets instead of bumping the vendor to pick up
DescribeSubnetsPages.  Even if we do overflow DescribeSubnets with
untagged subnets, VPC deletion will fail and we'll get another pass at
deleting tagged subnets when we come around to the next deleteEC2VPC
attempt.
jhixson74 pushed a commit to jhixson74/installer that referenced this pull request Dec 6, 2019
Sometimes CI leaks untagged subnets.  Because we are allowed to remove
all resources from within a cluster-owned VPC, add a ByVPC walker to
remove these indirectly-owned subnets.

DescribeSubnetsPages has a strange history.  It was initially added in
aws/aws-sdk-go@3664ecc7da (Add initial implementation of pagination,
2015-03-23, aws/aws-sdk-go#247) but was removed in
aws/aws-sdk-go@bad551feb8 (Add support for multi-token pagination
rules, 2015-03-27) as a later step in that same pull request.  It
finally landed in master via aws/aws-sdk-go@52cd98f1ed (Release
v1.19.30, 2019-05-14, aws/aws-sdk-go#2599), but we only vendor
v1.16.14.  It doesn't seem like "zounds of untagged subnets" is a
high-probability thing, so I'm just using the unpaginated
DescribeSubnets instead of bumping the vendor to pick up
DescribeSubnetsPages.  Even if we do overflow DescribeSubnets with
untagged subnets, VPC deletion will fail and we'll get another pass at
deleting tagged subnets when we come around to the next deleteEC2VPC
attempt.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant