solarmosaic-kflorence
commented
3 years ago Here is a more thorough example. This is the project structure (this project exists in our monorepo repository at location: ./libraries/terraform/aws/bucket-object):
.
├── main.tf
├── modules
│ └── policies
│ ├── main.tf
│ ├── outputs.tf
│ └── variables.tf
├── outputs.tf
├── readme.md
├── variables.tf
└── versions.tfInside main.tf there is a module reference:
module "session" {
source = "s3::https://s3.amazonaws.com/<REDACTED>/terraform/terraform-aws-session/terraform-aws-session_v0.2.2.zip"
}Starting with no .terraform cache, I run terraform init in the root of the project...
➜ monorepo git:(feature/foo) cd libraries/terraform/aws/bucket-object
➜ bucket-object git:(feature/foo) terraform init
Initializing modules...
Downloading s3::https://s3.amazonaws.com/<REDACTED>/terraform/terraform-aws-session/terraform-aws-session_v0.2.2.zip for session...
- session in .terraform/modules/session
Initializing the backend...
Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Installing hashicorp/aws v3.61.0...
- Installed hashicorp/aws v3.61.0 (signed by HashiCorp)
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.The project .terraform cache folder now has the following structure:
.
├── modules
│ ├── modules.json
│ └── session
│ ├── main.tf
│ ├── modules
│ │ ├── meta
│ │ │ └── outputs.tf
│ │ └── policies
│ │ ├── main.tf
│ │ └── outputs.tf
│ ├── outputs.tf
│ └── versions.tf
└── providers
└── registry.terraform.io
└── hashicorp
└── aws
└── 3.61.0
└── darwin_amd64
└── terraform-provider-aws_v3.61.0_x5The modules/modules.json file has the following content:
{"Modules":[{"Key":"","Source":"","Dir":"."},{"Key":"session","Source":"s3::https://s3.amazonaws.com/<REDACTED>/terraform/terraform-aws-session/terraform-aws-session_v0.2.2.zip","Dir":".terraform/modules/session"}]}IntelliJ now correctly resolves this module from the cache, so the modules cache at the root of the project work fine. Now let's resolve the module references for the ./modules/policies sub-module, which contains the following in it's main.tf file:
module "session" {
source = "s3::https://s3.amazonaws.com/<REDACTED>/terraform/terraform-aws-session/terraform-aws-session_v0.2.2.zip//modules/policies"
}Again starting from having no .terraform cache, I navigate into the sub-module folder and run terraform init:
➜ bucket-object git:(feature/foo) cd modules/policies
➜ policies git:(feature/foo) terraform init
Initializing modules...
Downloading s3::https://s3.amazonaws.com/<REDACTED>/terraform/terraform-aws-session/terraform-aws-session_v0.2.2.zip for session...
- session in .terraform/modules/session/modules/policies
Initializing the backend...
Initializing provider plugins...
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.The ./modules/policies/.terraform cache directory now has the following structure:
.
└── modules
├── modules.json
└── session
├── main.tf
├── modules
│ ├── meta
│ │ └── outputs.tf
│ └── policies
│ ├── main.tf
│ └── outputs.tf
├── outputs.tf
└── versions.tfThe modules/modules.json file has the following content:
{"Modules":[{"Key":"","Source":"","Dir":"."},{"Key":"session","Source":"s3::https://s3.amazonaws.com/<REDACTED>/terraform/terraform-aws-session/terraform-aws-session_v0.2.2.zip//modules/policies","Dir":".terraform/modules/session/modules/policies"}]}However, IntelliJ cannot resolve the module:
ambis
Xerkus
mohamed-haidara-cko
jzburns
danpoland
lonegunmanb
shuliakovsky
gchamon
rashidnhm
userbradley
fabio-filho
lozuwa
psantus
mirzazeyrek
Prerequisites
Installation details
Help->About->Copy to Clipboard)Settings->Plugins) -0.7.14terraform -v) -v1.0.10(darwin_amd64)Terraform Configuration Files
And here is the project folder (including
.terraformcache):Exception
N/A
Expected Behavior
The HCL plugin should be able to reference any module cached in the
./.terraformin the current directory. We are using Terraform inside of a monorepo, so we have several directories scattered around with Terraform configuration. I have noticed in some project folders we do not have this issue and in others we do. It seems to happen most often within sub-modules (e.g../modules/bar, relative to the project root), or when referencing sub-folders of a module, for example:Actual Behavior
The module exists, of course, and is downloaded and cached in the
.terraformfolder. Performing Terraform CLI commands in the directory will succeed. It's just a problem with the plugin cache.In the example we are downloading the module from S3, but it shouldn't matter what the source is. Notably, though, I haven't seen this happen with a local module reference (e.g.
source = "../../path/to/module").Steps to Reproduce
See the comment below https://github.com/VladRassokhin/intellij-hcl/issues/365#issuecomment-981972598