-
Notifications
You must be signed in to change notification settings - Fork 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
deps: upgrade aws-sdk-go from v1 to v2 #24720
Conversation
@mismithhisler can you check the impact of this change on binary size? In #24701 I noted that updating this library doesn't update the dependencies that have it as a transient dependency for v1, and so we'll be carrying around both versions. |
@tgross I saw that and using It looks like it added 2.7MB to the binary size. |
Eh, ok. That stinks but not worth delaying the fix for. It'd be nice if we could nudge along the other HashiCorp libraries that are pulling this in. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this @mismithhisler! I've added a couple of inline comments/questions which would be good to resolve before merging but looks and works great.
I ran this locally on macOS and everything looked OK, with the correct message showing up in the logs:
client.fingerprint_mgr.env_aws: error querying AWS IDMS URL, skipping
I then ran this PR on an AWS cluster and the node attributes looked how I would expect:
$ nomad node status -verbose bd306835 |grep aws
kernel.version = 6.8.0-1009-aws
platform.aws.ami-id = ami-0474244c88b835731
platform.aws.instance-life-cycle = on-demand
platform.aws.instance-type = m5.xlarge
platform.aws.placement.availability-zone = eu-west-2a
unique.platform.aws.hostname = ip-10-0-1-15.eu-west-2.compute.internal
unique.platform.aws.instance-id = i-0765dd85a71bc86bb
unique.platform.aws.local-hostname = ip-10-0-1-15.eu-west-2.compute.internal
unique.platform.aws.local-ipv4 = 10.0.1.15
unique.platform.aws.mac = 06:72:45:96:05:15
unique.platform.aws.public-ipv4 = xx.xxx.xxx.xxx
The output from the same Nomad client running the official v1.9.4 release:
$ nomad node status -verbose bd306835 |grep aws
kernel.version = 6.8.0-1009-aws
platform.aws.ami-id = ami-0474244c88b835731
platform.aws.instance-life-cycle = on-demand
platform.aws.instance-type = m5.xlarge
platform.aws.placement.availability-zone = eu-west-2a
unique.platform.aws.hostname = ip-10-0-1-15.eu-west-2.compute.internal
unique.platform.aws.instance-id = i-0765dd85a71bc86bb
unique.platform.aws.local-hostname = ip-10-0-1-15.eu-west-2.compute.internal
unique.platform.aws.local-ipv4 = 10.0.1.15
unique.platform.aws.mac = 06:72:45:96:05:15
unique.platform.aws.public-ipv4 = xx.xxx.xxx.xxx
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Nice refactoring work on the error/response body reading.
Description
Upgrades aws-sdk-go from v1 to v2 as the v1 library is in maintenance mode.
Closes GH #24680
Testing & Reproduction steps
Links
Contributor Checklist
changelog entry using the
make cl
command.ensure regressions will be caught.
and job configuration, please update the Nomad website documentation to reflect this. Refer to
the website README for docs guidelines. Please also consider whether the
change requires notes within the upgrade guide.
Reviewer Checklist
backporting document.
in the majority of situations. The main exceptions are long-lived feature branches or merges where
history should be preserved.
within the public repository.