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

fix: bump aws-sdk-go-base/v2 from v2.0.0-beta.58 to v2.0.0-beta.62 #36625

Merged
merged 1 commit into from
Mar 6, 2025

Conversation

sebastianmarines
Copy link
Contributor

Bump aws-sdk-go-base/v2 version

Fixes #36624

Target Release

1.11.x

CHANGELOG entry

bump aws-sdk-go-base/v2 from v2.0.0-beta.58 to v2.0.0-beta.62

  • This change is user-facing and I added a changelog entry.
  • This change is not user-facing.

@sebastianmarines sebastianmarines requested a review from a team as a code owner March 4, 2025 07:14
Copy link

hashicorp-cla-app bot commented Mar 4, 2025

CLA assistant check
All committers have signed the CLA.

@crw
Copy link
Contributor

crw commented Mar 4, 2025

Thanks for this submission, this will need to be reviewed by the HashiCorp AWS provider team and it is in their queue. Thanks again!

Copy link
Member

@bschaatsbergen bschaatsbergen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @sebastianmarines,

Thank you for taking a look at this, that's great. As #36624 (comment) states, it looks like hashicorp/aws-sdk-go-base#1248 added support for mx-central-1 which was released under v2.0.0-beta.61 (2025-01-15).

Thank you for bumping it to the latest beta release, which includes another region as well. Instead of updating the indirect dependency in the root go.mod, could you update the go.mod I tagged in the review comment?

@sebastianmarines sebastianmarines requested a review from a team as a code owner March 4, 2025 22:55
@jar-b jar-b requested review from a team as code owners March 5, 2025 15:21
@jar-b jar-b added the 1.11-backport If you add this label to a PR before merging, backport-assistant will open a new PR once merged label Mar 5, 2025
jar-b
jar-b previously approved these changes Mar 5, 2025
Copy link
Member

@jar-b jar-b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🎉

% TF_ACC=1 go test ./...
ok      github.com/hashicorp/terraform/internal/backend/remote-state/s3 207.393s

@jar-b jar-b requested a review from bschaatsbergen March 5, 2025 15:40
bschaatsbergen
bschaatsbergen previously approved these changes Mar 5, 2025
This upgrade will add support for S3 backends in several new regions,
including `mx-central-1`.
@jar-b jar-b dismissed stale reviews from bschaatsbergen and themself via 9237b11 March 6, 2025 16:10
@jar-b jar-b force-pushed the update-aws-sdk-go-base branch from a17b794 to 9237b11 Compare March 6, 2025 16:10
@jar-b
Copy link
Member

jar-b commented Mar 6, 2025

Thanks for your contribution, @sebastianmarines!

@jar-b jar-b merged commit 9ac4b3a into hashicorp:main Mar 6, 2025
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.11-backport If you add this label to a PR before merging, backport-assistant will open a new PR once merged backend/s3 upstream
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invalid AWS Region when creating S3 backend in mx-central-1 region
5 participants