-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Module not found, may need to be downloaded using 'terraform get' #8724
Comments
|
Happened to me too, had to delete old modules in Does terraform encode something version-specific in its modules, which makes this an expected behavior? I don't remember having to do this between 0.7.1 and 0.7.2, but definitely between 0.7.2 and 0.7.3. |
This is mentioned in the CHANGELOG as a slight BC-change in 0.7.3: we changed some internal structures requiring you to run |
Thanks for the feedback. Admittedly, I didn't read the changelog. But I did run |
Yeah, this definitely doesn't seem to be working as expected. I ran |
I'm not sure if it's relevant, but we are using relative paths for our modules.
|
If I revert #8398 then I no longer get an error. |
I've created a small repository that can be used to reproduce the issue, see https://github.com/joshuaspence/terraform-issue8724-test. To reproduce the error with Terraform 0.7.3, follow these steps:
It could be our use of symlinks that is causing the issue. We use symlinks so that we can use the same set of Terraform files to produce multiple identical environments (eg. dev, staging and production). |
It looks like I can't reopen this issue but it would be appreciated if someone else could re-open it for me. |
reopened |
Relevant comment/commit here that introduced this: #8398 (comment) I think most importantly in addition to simply reverting we'll need to add regression testing around this since I was able to get the above commit in without any failing tests. |
We also use relative paths to (many) modules here, and have not been able to get 0.7.3 to run in Atlas. Nothing I've tried yet seems to make a difference, including deleting my existing local modules before doing a get/push. For the moment I've reverted to 0.7.2 across the board. UPDATE: I just tried 0.7.4 and it is displaying the same behavior as 0.7.3 was re: existing environments in Atlas. Not fixed... |
hashicorp/go-getter#28 seems to be the root issue here, causing an invalid module path when starting from a relative symlink. |
Also confirming an issue in 0.7.3 with relative paths to modules. Using 0.7.2 locally and setting Atlas to run the environment with 0.7.2 resolved the issue for now. |
Ah hah, @jbardin has a nice fix up that looks great. |
For some reason, Terraform 0.7.3 was working for some people in our company but not for others. As a result, I am now unable to use Terraform 0.7.2 (because the state file was last updated with Terraform 0.7.3) and also unable to use Terraform 0.7.3 (because of this issue). Is there any chance of cutting a new release soon? |
I see that this has been closed, but it doesn't seem to be included in the CHANGELOG for version 0.7.4 or 0.7.5, nor has the behavior changed. Has this not been included in a release yet? |
I'm using terraform v0.10.7 on osx and I am getting the same error. Is this expected?
This seems like it will be less than ideal when I am developing on my child module. Will I need to run terraform get then terraform apply each time I make a change? |
@srossross-tableau try running |
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. |
After updating to Terraform 0.7.3, I am getting the following error when running
terraform plan
:This issue doesn't seem to occur in Terraform 0.7.2. I will work on a MWE to reproduce this issue.
The text was updated successfully, but these errors were encountered: