-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
AWS version mismatch between several modules #41
Comments
I had the same problem, the only version that I could run is the one with the tag 0.8.0, before that it only works with terraform 0.12 |
Sorry about that! We might have some pinning that needs updating. We have evolved our thinking on pinning and now require a minimum known working provider (>=) version and core version. We no longer recommend using (~>) and still have remnants of that. We will gladly accept and promptly review all PRs to correct pinning. Ping us on slack if we don't respond in a timely manner. |
Thanks @osterman. Raised PR's for the modules causing issues for aws plugin with version |
I believe this has been fixed. If not, please open a new issue. |
Describe the Bug
Hello Team -
I started using
terraform-aws-eks-node-group
module and it uses providerhashicorp/aws
version>=3.0.*
while the other modules uses version~> 2.0
. This is causing the issue when nodegroups are used with loadbalancers, keypair and rds modules.Terraform version:
v0.13.5
Running
terraform init
throwsProviders list
Based on the modules i'm using here are the modules that needs to be changed from
~> 2.0
to>= 2.0
Expected Behavior
All the plugins/providers should have been installed without any issue
Steps to Reproduce
Use eks-node-group module with latest tag (0.13.0) with aws-alb and aws-rds modules with latest tags.
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:
Output
terraform -version
:Thanks.
The text was updated successfully, but these errors were encountered: