You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version 5 of the officlal AWS provider for Terraform was released back in May of this year (2023). Since then, there have been no v4 releases (latest one, v4.67.0, was in May 11), though I was unable to find official announcements or articles backing up the lack of support for v4.
While not overly complex, the changes required to upgrade this module from v4 to v5 should be looked over carefully. This part of the documentation explains what to expect when upgrading.
Expected Behavior
Modules using version 5 of the AWS provider should be able to invoke this module without generating any warnings, regressions, or unexpected behavior.
Use Case
Anyone writing Terraform modules / configuration around version 5 of the AWS provider and also invoking this module will require support.
Alternatives Considered
Continuing to support this module built around v4 of the provider means passing on bug fixes and improvements that come with version 5 of the AWS provider.
The text was updated successfully, but these errors were encountered:
Describe the Feature
Version 5 of the officlal AWS provider for Terraform was released back in May of this year (2023). Since then, there have been no v4 releases (latest one, v4.67.0, was in May 11), though I was unable to find official announcements or articles backing up the lack of support for v4.
While not overly complex, the changes required to upgrade this module from v4 to v5 should be looked over carefully. This part of the documentation explains what to expect when upgrading.
Expected Behavior
Modules using version 5 of the AWS provider should be able to invoke this module without generating any warnings, regressions, or unexpected behavior.
Use Case
Anyone writing Terraform modules / configuration around version 5 of the AWS provider and also invoking this module will require support.
Alternatives Considered
Continuing to support this module built around v4 of the provider means passing on bug fixes and improvements that come with version 5 of the AWS provider.
The text was updated successfully, but these errors were encountered: