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: Reduce required versions for Terraform and AWS provider #1

Conversation

bryantbiggs
Copy link
Member

Description

  • Reduce required versions for Terraform and AWS provider

Motivation and Context

Breaking Changes

  • No since we are reducing the version requirements (expanding capability) and there isn't anything required by the configs used to dictate v4.0 or Terraform v1.0 (was just picked as the current "starting point")

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@bryantbiggs
Copy link
Member Author

@antonbabenko

@junaid-ali
Copy link

@bryantbiggs I'm wondering that instead of downgrading the other versions, if we need to update the terraform version in this repo: https://github.com/terraform-aws-modules/terraform-aws-kms/blob/master/versions.tf#L2

@bryantbiggs
Copy link
Member Author

no. because I added the KMS module to the EKS module terraform-aws-modules/terraform-aws-eks#2121 - that is what is forcing the overall EKS module to require Terraform v1.0+

There isn't anything in this module that requires Terraform v1.0+ or AWS v4.0+, those are just the "defaults" I start with on modules these days. But since this module is embedded in other modules, we have to ensure it meets the minimum. Therefore, reducing its required versions here, and the bumping the version used on the EKS module - that will put the EKS module back on par with the versions it uses today. We don't want to bump those because that would incur a major release due to breaking changes (more restrictions)

Copy link
Member

@antonbabenko antonbabenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this PR because, as you say, it is a small resource module which is used in a bigger/EKS one.

@bryantbiggs
Copy link
Member Author

ah, we didn't add this repo under meta yet - @antonbabenko are you able to merge this one when you get a chance 🙏🏽

@antonbabenko antonbabenko merged commit f80bc66 into terraform-aws-modules:master Jun 28, 2022
antonbabenko pushed a commit that referenced this pull request Jun 28, 2022
### [1.0.1](v1.0.0...v1.0.1) (2022-06-28)

### Bug Fixes

* Reduce required versions for Terraform and AWS provider ([#1](#1)) ([f80bc66](f80bc66))
@antonbabenko
Copy link
Member

This PR is included in version 1.0.1 🎉

@bryantbiggs bryantbiggs deleted the fix/rewind-terraform-version branch June 28, 2022 19:00
@antonbabenko
Copy link
Member

@bryantbiggs I have just fixed permissions for KMS and global accelerator module you imported a few weeks ago.

@bryantbiggs
Copy link
Member Author

awesome, thank you!

@junaid-ali
Copy link

no. because I added the KMS module to the EKS module terraform-aws-modules/terraform-aws-eks#2121 - that is what is forcing the overall EKS module to require Terraform v1.0+

There isn't anything in this module that requires Terraform v1.0+ or AWS v4.0+, those are just the "defaults" I start with on modules these days. But since this module is embedded in other modules, we have to ensure it meets the minimum. Therefore, reducing its required versions here, and the bumping the version used on the EKS module - that will put the EKS module back on par with the versions it uses today. We don't want to bump those because that would incur a major release due to breaking changes (more restrictions)

Oh sorry, I thought the PR was in the terraform-aws-eks repo 😅

@github-actions
Copy link

github-actions bot commented Nov 8, 2022

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 Nov 8, 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.

3 participants