Skip to content
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

fix: Pin version to v3 due to number of breaking changes in v4 #136

Merged
merged 2 commits into from
Feb 10, 2022

Conversation

bryantbiggs
Copy link
Member

Description

  • Pin version to v3 due to number of breaking changes in v4
  • Fix mismatched value type error when using tomap({})

Note: running pre-comit locally fails the checks. It seems like its not respecting the ~> 3.x and trying to validate against 4x which shows as a failure. However, going into the example directories and running terraform init -upgrade=true && terraform plan works as expected

Motivation and Context

  • Temporarily pin version until we can address v4 changes

Breaking Changes

How Has This Been Tested?

  • I have tested and validated these changes using one or more of the provided examples/* projects
    • Tested with local plans

@bryantbiggs
Copy link
Member Author

@antonbabenko not sure what to do here - it looks like either terraform validate or something within pre-commit is not respecting the v3.x pin. locally running an init and plan works fine though

@antonbabenko
Copy link
Member

There were several improvements (aka "potential bugs") in pre-commit-terraform during today but the fix d362eb6 was still required. Time to merge this one :)

@antonbabenko antonbabenko merged commit 7dd9a65 into terraform-aws-modules:master Feb 10, 2022
antonbabenko pushed a commit that referenced this pull request Feb 10, 2022
### [2.14.1](v2.14.0...v2.14.1) (2022-02-10)

### Bug Fixes

* Pin version to v3 due to number of breaking changes in v4 ([#136](#136)) ([7dd9a65](7dd9a65))
@antonbabenko
Copy link
Member

This PR is included in version 2.14.1 🎉

@bryantbiggs bryantbiggs deleted the fix/v4-support branch February 10, 2022 19:47
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants