Skip to content

fix: version pin to avoid hashicorp/aws provider bug #266

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

Closed
wants to merge 1 commit into from

Conversation

westonplatter
Copy link

what

  • Stay below a problematic hasicorp/aws provider version.
  • Hashicorp is working on patch in 5.86.1, but until a solution lands well, better to stay below the turbulence.

why

  • The intent is to avoid the v5.86.0 release, which moved from the Terraform Plugin SDK to Terraform Plugin Framework.
  • The v5.86.0 code changes the default lifecycle value and going forward requires that you use a 5.86.0 or greater provider.

references

The intent is to avoid 5.86.0. Github issue detailing bug,
hashicorp/terraform-provider-aws#41296
@westonplatter westonplatter requested review from a team as code owners February 10, 2025 23:22
@mergify mergify bot added the triage Needs triage label Feb 10, 2025
@nitrocode
Copy link
Member

This may not be an issue any longer.

Usually the cp modules don't pin an upperbound since the module caller has the ability to pin in their versions.tf file so this gives people flexibility. By pinning the upperbound, we lose that and for that reason we need to close this PR.

Sorry about that. Please send more PRs and we will review when time permits. Thank you for the contribution.

@nitrocode nitrocode closed this May 6, 2025
@mergify mergify bot removed the triage Needs triage label May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants