Upgrade terraform-provider-aws to v5.32.0 #3253
Assignees
Labels
Comments
|
Picking this up now I understand there's some complications with legacy bucket. I'll have a look. |
t0yv0
added a commit
that referenced
this issue
Jan 23, 2024
Fixes #3253 This PR upgrades the provider to match upstream provider version v5.32.0. List of unusual things that defeated upgrade-provider and required manual intervention: - The patch for elbv2 target workaround in #2517 does not apply cleanly to new upstream, had to be redone; I've tested manually that 2517 does not reproduce on top of the new provider, but need to backlog adding a test for it; the relevant ticket is in #2749 - Upstream is gradually removing AWS Go SDK v1. This affected legacy bucket resource that Pulumi retains in spite of upstream having it removed. This is now working again but required another invasive patch to undo upstream changes. - New "verified permissions" module needed to be registered in resources.go to support automatic module inference. - Several new Plugin Framework based resources required patching to support tags; this is slowing us down until we can implement #2962 - Run test of provider shim was breaking as it didn't get all the dependencies, now fixed - Patch from #3290 wouldn't apply because of wrong format (`make upstream.rebase` broken) - had to reformat it - doc_edits.go would keep appending edits to replacements.json; this is fixed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Release details: https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.32.0
The text was updated successfully, but these errors were encountered: