Martin Atkins 30b7040e95 core: Validate module references ... Previously we were making an invalid assumption in evaluating module call references (like module.foo) that the module must exist, which is incorrect for that particular case because it's a reference to a child module, not to an object within the current module. However, now that we have the mechanism for static validation of references, we'll deal with this one there so it can be caught sooner. That then makes the original assumption valid, though for a different reason. This is verified by two new context tests for validation: - TestContext2Validate_invalidModuleRef - TestContext2Validate_invalidModuleOutputRef		2018-11-28 13:19:57 -08:00
..
testdata/config-fixture	repl: Fix tests	2018-10-16 19:14:11 -07:00
format.go	command: update "terraform console" for HCL2	2018-10-16 18:46:46 -07:00
repl.go	repl: package for TF REPL	2016-11-13 23:17:03 -08:00
session_test.go	core: Validate module references	2018-11-28 13:19:57 -08:00
session.go	command: update "terraform console" for HCL2	2018-10-16 18:46:46 -07:00