Skip to content
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

Bump aws-sdk-go from 1.44.122 to 1.44.298 #33522

Closed

Conversation

johnnywalker
Copy link

Upgrade aws-sdk-go to v1.44.298, which enables support for Identity Center/SSO.

Ref: https://github.com/aws/aws-sdk-go/releases/tag/v1.44.298

Fixes #32448
Fixes #32465

Target Release

1.5.x

Draft CHANGELOG entry

Bump aws-sdk-go from 1.44.122 to 1.44.298 (support SSO in AWS backend)

BUG FIXES

When using the aws backend, Terraform no longer throws:

╷
│ Error: error configuring S3 Backend: Error creating AWS session: profile "xxx" is configured to use SSO but is missing required configuration: sso_region, sso_start_url
│ 
│ 
╵

@hashicorp-cla
Copy link

hashicorp-cla commented Jul 13, 2023

CLA assistant check
All committers have signed the CLA.

@crw
Copy link
Collaborator

crw commented Jul 13, 2023

Thanks for this submission! I'll raise it in triage.

@johnnywalker
Copy link
Author

Very welcome! Thanks for taking a look.

@kmoe kmoe requested a review from a team July 14, 2023 14:21
@crw
Copy link
Collaborator

crw commented Jul 14, 2023

As this library is only used by this backend, it has been referred to the AWS Provider team for review. Thanks!

@johnnywalker johnnywalker requested a review from a team as a code owner July 18, 2023 20:34
@johnnywalker johnnywalker changed the base branch from main to v1.5 July 18, 2023 20:34
@johnnywalker
Copy link
Author

@crw Sorry for the confusion, but my PR should have targeted v1.5 instead of main. I've updated the base and fork accordingly.

@crw
Copy link
Collaborator

crw commented Jul 18, 2023

@johnnywalker have you seen this PR / thread as well? I think we can probably close this PR as the work will be done in stages by the provider team - what do you think?

#33469 (comment)

@david-yu david-yu removed the request for review from a team July 18, 2023 23:37
@johnnywalker
Copy link
Author

@crw Yes sir I took a look at that but wasn't sure about the timeline. In particular, that comment mentions rolling out the change with several releases, so I assume it's a bit more protracted.

This PR effectively backports SSO support for the S3 backend to v1.5 and can be used immediately. I'm running it locally and thoroughly enjoying the SSO support! If others agree, I think it would be very helpful to merge this to v1.5 in the interim.

@crw
Copy link
Collaborator

crw commented Jul 19, 2023

Interesting. It may be problematic merging only to 1.5 - if the other change isn't baked by the time 1.6 rolls out, then this feature would regress. In any case, I will leave this PR open for the AWS provider team to review as they have time.

@michailw
Copy link

Just leaving the note - the AWS provider team merged the same bump on the AWS provider side and released it with the 5.8.0 version of the AWS provider.

hashicorp/terraform-provider-aws#28263
https://github.com/hashicorp/terraform-provider-aws/pull/32426/files

@crw
Copy link
Collaborator

crw commented Jul 25, 2023

@johnnywalker Just a heads-up, this would need to be merged to main (and then we would backport it to 1.5). I need to check with @gdavison to see if we can merge this without getting in the way of what he has planned - I'll follow up on that and get back to you.

@crw
Copy link
Collaborator

crw commented Jul 27, 2023

@johnnywalker Confirmed that this can be merged without impacting the upgrade to 2.x, so when you get a chance please re-target to main and I can get this reviewed and merged. Thanks!

@jBouyoud
Copy link

@crw , I just re-create a new PR on main target

@crw
Copy link
Collaborator

crw commented Jul 31, 2023

Thanks! We can move the further discussion there.

@crw crw closed this Jul 31, 2023
@johnnywalker
Copy link
Author

@crw @jBouyoud Sorry for the late response. I'll continue discussion on #33607 , but I initially applied these changes to main and ran into problems using the updated version locally. Perhaps this has been resolved already, but I assumed main included work-in-progress for migrating to aws-sdk-go-v2. In particular, there are quite a few aws-sdk-go-v2 dependencies listed in go.sum now, and these originated in 9f6a3ba#diff-3295df7234525439d778f1b282d146a4f1ff6b415248aaac074e8042d9f42d63.

Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
6 participants