You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created this PR to better document and report errors based on how source_path is interpreted currently.
However, now I see that the current behavior is more of a problem than before. I've created an ./examples/example1 dir for my module which has a main.tf that calls my custom module with a source of ../../. When I run terraform plan from within this examples directory, the source_path specified in the source is being interpreted relative to this example1 directory instead of from the module's root directory.
This causes a source_path must be set error.
Recommended Fix:
Interpret source_paths relative to the location of the terraform file in which they are named.
The text was updated successfully, but these errors were encountered:
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.
I created this PR to better document and report errors based on how
source_path
is interpreted currently.However, now I see that the current behavior is more of a problem than before. I've created an
./examples/example1
dir for my module which has amain.tf
that calls my custom module with asource
of../../
. When I runterraform plan
from within this examples directory, thesource_path
specified in the source is being interpreted relative to thisexample1
directory instead of from the module's root directory.This causes a
source_path must be set
error.Recommended Fix:
Interpret
source_path
s relative to the location of the terraform file in which they are named.The text was updated successfully, but these errors were encountered: