Skip to content

chore!: Update AWS provider version to 6.12.0 across all modules and … #517

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

chore!: Update AWS provider version to 6.12.0 across all modules and … #517

wants to merge 1 commit into from

Conversation

barnou
Copy link

@barnou barnou commented Sep 12, 2025 •
edited
Loading

Description

  • Update module to use aws provider v6
  • Update all versions of the modules used in the example directory to use version v6 of the aws provider.

Motivation and Context

  • We wish to standardise the versions of our AWS providers across all our projects, and to do so, we require this module to be updated.
  • It's a prerequisite to use the region attribute in the future

Breaking Changes

Yes. AWS provider version upgrade to v6.

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@baptiste-arnou-aircall
chore!: update AWS provider version to 6.12.0 across all modules and …
662cdc0 
…examples

- Updated AWS provider version from >= 5.89 to >= 6.12.0 in README and versions.tf files for all examples and modules.
- Adjusted VPC module version from ~> 5.0 to ~> 6.0 in relevant examples.
- Updated KMS module version from ~> 2.0 to ~> 4.0 in examples where applicable.
@barnou barnou changed the title chore!: update AWS provider version to 6.12.0 across all modules and … chore!: Update AWS provider version to 6.12.0 across all modules and … Sep 12, 2025
@bryantbiggs
Copy link
Member

there is no reason to raise the MSV just for you to "standardize" the version used in your configurations. we only pin the minimum version so you are free to use any version later than that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@barnou @bryantbiggs @baptiste-arnou-aircall