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

Terraform v0.12 not supported here anymore - use v0.13 #159

Open
andrejs-sisojevs opened this issue Nov 11, 2020 · 1 comment
Open

Terraform v0.12 not supported here anymore - use v0.13 #159

andrejs-sisojevs opened this issue Nov 11, 2020 · 1 comment

Comments

@andrejs-sisojevs
Copy link

Terraform v0.12 won't work anymore with recent changes in master (see errors below).
Using Terraform v0.13.5 works fine.
I suggest whoever introduced the breaking changes, also update README.md and other docs to require tf v0.13.

$ terraform init
Initializing modules...
There are some problems with the configuration, described below.

The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and providers need to be installed.

Error: Reserved argument name in module block

  on .terraform/modules/jx/main.tf line 184, in module "vault":
 184:   count  = ! var.gsm ? 1 : 0

The name "count" is reserved for use in a future version of Terraform.


Error: Reserved argument name in module block

  on .terraform/modules/jx/main.tf line 202, in module "gsm":
 202:   count  = var.gsm && ! var.jx2 ? 1 : 0

The name "count" is reserved for use in a future version of Terraform.


Error: Reserved argument name in module block

  on .terraform/modules/jx/modules/cluster/main.tf line 80, in module "jx-health":
  80:   count  = var.jx2 ? 0 : 1

The name "count" is reserved for use in a future version of Terraform.


Error: Reserved argument name in module block

  on .terraform/modules/jx/modules/cluster/main.tf line 83, in module "jx-health":
  83:   depends_on = [

The name "depends_on" is reserved for use in a future version of Terraform.
@jenkins-x-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants