-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
feat!: Update to support AWS provider v3.75 and newer (including v4.x) #139
Conversation
Is there a way for me to use this now? Rather than waiting for it to be merged? How is that done in the Terraform world. Also 👍 for making the changes. |
It's definitely not recommended to use in anything other than testing, and is probably very highly discouraged, but you can do this: module "s3" {
source = "git::https://github.com/terraform-aws-modules/terraform-aws-s3-bucket.git?ref=fix-tf-provider-v4"
} |
Thanks Anton, |
HI All, What needs to happen to get this across the finish line? I'd be happy to contribute where I can. This module has been a great help for me and I'd like for this get completed and merged. |
hey @antonbabenko is there anything we can do to get this through the finish line? |
Hello everyone! I have been recovering and resumed working on this PR earlier today after some thinking about potential resolutions mentioned here (hashicorp/terraform-provider-aws#23106). One of the things I have been thinking about was how to make this module compatible with v3 AND v4 to minimize state migration for resources. Anyway, I plan to finish this PR and have support for AWS provider v4 as soon as possible - Tuesday, 29th of March. |
in regards to state migration using moved blocks would be an easy win? no need for manual state moves by anyone? https://www.terraform.io/language/modules/develop/refactoring |
versions.tf
Outdated
@@ -4,7 +4,7 @@ terraform { | |||
required_providers { | |||
aws = { | |||
source = "hashicorp/aws" | |||
version = "~> 3.69" | |||
version = ">= 4.2.0" |
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.
version = ">= 4.2.0" | |
version = ">= 3.75.0" |
Hi @antonbabenko
Thanks for your work on this.
Actually, Hashicorp "backported" those breaking changes for S3 resources into AWS provider version 3.75.0
.
So I think this is a clear way to keep the code with 3.x
release unless all major modules will support 4.x
in full.
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.
Yes, I will incorporate this change also. Thank you!
This PR is included in version 3.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. |
Breaking changes:
UPGRADE-3.0.md
Fixes #137
Closes #138