-
-
Notifications
You must be signed in to change notification settings - Fork 91
feat!: Upgrade AWS provider and min required Terraform version to 6.0 and 1.5.7 respectively
#36
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
Conversation
|
Hello team, Thanks a lot for your review. Let me know if there's anything to fix / change. Bests. |
|
thank you - this is a breaking change and given that the provider is very recent, we will probably wait to see the level of stability and what other changes need to be made here as part of a breaking change before this is merged |
|
Perfect thanks @bryantbiggs, yes that's wise. let's wait and see. |
6.0 and 1.5.7 respectively
bryantbiggs
left a comment
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.
thank you!
## [4.0.0](v3.1.1...v4.0.0) (2025-07-05) ### ⚠ BREAKING CHANGES * Upgrade AWS provider and min required Terraform version to `6.0` and `1.5.7` respectively (#36) ### Features * Upgrade AWS provider and min required Terraform version to `6.0` and `1.5.7` respectively ([#36](#36)) ([210736c](210736c))
|
This PR is included in version 4.0.0 🎉 |
|
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 issues. 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. |
Description
regionparameter to specify the AWS region for the resources created if different from the provider region.anyvariable types have been replaced with full variable definitions usingoptional()variable attributesMotivation and Context
regionin resources without having to use aliased providersBreaking Changes
key_statements.conditionshas been changed tokey_statement.conditionto match the underlying APIgrants.constraintssupport multiple constraints and therefore its type has been changed to a list. You can simply wrap your currentconstraintsin brackets ([]) to resolve any diffs; see the updated example in this PRHow Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request