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 version above 1.2.6 brakes module #173

Closed
schrill opened this issue Aug 11, 2022 · 5 comments
Closed

Terraform version above 1.2.6 brakes module #173

schrill opened this issue Aug 11, 2022 · 5 comments

Comments

@schrill
Copy link

schrill commented Aug 11, 2022

Description

For some reason module syntax is no longer valid after upgrade to version 1.2.7, resulting in an error message on every argument that is not expected here.

│ Error: Unsupported argument │ │ on s3.tf line 8, in module "s3_bucket": │ 8: bucket = var.bucket_full_name == "" ? "${var.project_env}.${local.bucket_name}" : var.bucket_full_name │ │ An argument named "bucket" is not expected here.

@schrill schrill changed the title Terraform version above 1.2.6 breaks module Terraform version above 1.2.6 brakes module Aug 11, 2022
@jeohist
Copy link

jeohist commented Aug 11, 2022

This is not a problem with the module: hashicorp/terraform#31615
I've worked around it by just getting it from Git instead of the Terraform Module Registry.

@schrill
Copy link
Author

schrill commented Aug 11, 2022

Figured that braking changes were probably introduced inside TF it self but since other modules were functioning correctly didn't do much investigation.
Tnx for the link of the issue, pinned TF version to 1.2.6 for now...

@thomaskvnze
Copy link

We have similar issue. We use a module from the registry. Unfortunately, the module is downloaded, but the submodules used by that module are not, leading to half the module code not being there.

@antonbabenko
Copy link
Member

The issue belongs to Terraform 1.2.7 - hashicorp/terraform#31615.

Closing this issue here.

@github-actions
Copy link

I'm going to lock this issue 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 similar to this, 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

No branches or pull requests

4 participants