5 Commits (bd8cb41befa36456e88722c8335c5aa0807c85af)

Author	SHA1	Message	Date
Radek Simko	fc62afb6dc	fix: validate implied provider names in submodules (#31573)	4 years ago
James Bardin	a6968b5b20	Merge pull request #31060 from hashicorp/alisdair/fix-configload-snapshot-panic ... configs: Fix module loader nil pointer panic	4 years ago
Martin Atkins	ec421fe02d	configs: A test for the regression reported in #31081 ... 5417975946 addressed a regression in the logic for catching when the newer module meta-arguments are used in conjunction with the legacy practice of including provider configurations inside modules, where the check started incorrectly catching situations where the legacy nested provider configuration was in the same module as the child call using one of those meta-arguments. This is a regression test to catch if a similar bug arises in the future. Since it's testing validation rules that apply to an entire configuration tree, it ended up in a rather idiosyncratic location under the "configload" package, rather than directly in "configs". The "configs" package only knows how to load one module at a time, so it's harder to write a test like this in that context. Due to it being further removed from the code it is testing, I included a test for the correct error too in order to increase the chance that we'll learn if future changes in the "configs" package invalidate this regression test. I've verified that this new test fails without the change made in the earlier commit.	4 years ago
Alisdair McDiarmid	d1e35a3f7c	configs: Fix module loader nil pointer panic ... In configurations which have already been initialized, updating the source of a non-root module call to an invalid value could cause a nil pointer panic. This commit fixes the bug and adds test coverage.	4 years ago
Martin Atkins	31349a9c3a	Move configs/ to internal/configs/ ... This is part of a general effort to move all of Terraform's non-library package surface under internal in order to reinforce that these are for internal use within Terraform only. If you were previously importing packages under this prefix into an external codebase, you could pin to an earlier release tag as an interim solution until you've make a plan to achieve the same functionality some other way.	5 years ago