38 Commits (db08ee4ac59d5eb8bcfffc175489ebf461bf4a92)

Author	SHA1	Message	Date
Martin Atkins	8364383c35	Push plugin discovery down into command package ... Previously we did plugin discovery in the main package, but as we move towards versioned plugins we need more information available in order to resolve plugins, so we move this responsibility into the command package itself. For the moment this is just preserving the existing behavior as long as there are only internal and unversioned plugins present. This is the final state for provisioners in 0.10, since we don't want to support versioned provisioners yet. For providers this is just a checkpoint along the way, since further work is required to apply version constraints from configuration and support additional plugin search directories. The automatic plugin discovery behavior is not desirable for tests because we want to mock the plugins there, so we add a new backdoor for the tests to use to skip the plugin discovery and just provide their own mock implementations. Most of this diff is thus noisy rework of the tests to use this new mechanism.	9 years ago
James Bardin	ec00564be6	Clean up LockInfo and LockError and use them ... Gove LockInfo a Marshal method for easy serialization, and a String method for more readable output. Have the state.Locker implementations use LockError when possible to return LockInfo and an error.	9 years ago
James Bardin	5ca5a3c78a	Merge pull request #11724 from hashicorp/jbardin/state-locking ... add force-unlock command	9 years ago
Mitchell Hashimoto	0c97c5a3d9	command: tests should move to temporary cwd ... This fixes any issues where rogue tfstate files may appear in the cwd otherwise.	9 years ago
James Bardin	b80ae5e13e	Add source path argument to testLockState ... The new test pattern is to chdir into a temp location for the test, but the prevents us from locating the testdata directory in the source. Add a source path to testLockState so we can find the statelocker.go source.	9 years ago
James Bardin	9fa436e0bd	Add test for locked state in plan	9 years ago
Mitchell Hashimoto	b8c310c61e	command: update test failure to correct message	9 years ago
Mitchell Hashimoto	09e0727d5e	command/plan: revert test change on this output	9 years ago
Mitchell Hashimoto	ad7b063262	command: convert to use backends	9 years ago
Mitchell Hashimoto	36ff8b3c02	command/plan: show a warning when a plan file is given	9 years ago
Mitchell Hashimoto	7f87a0109b	command/plan: user friendly error if plan file given to plan command	9 years ago
Mitchell Hashimoto	609219fc65	command/meta: validate config immediately ... * config: test for validating multi-vars (passes) * command/plan: test invalid run * command/meta: validate module on load	10 years ago
Sander van Harmelen	d97b24e3c1	Add tests and fix last issues	10 years ago
Paul Hinze	ae73aa2fb4	core: Do not persist state after plans ... This makes the behavior of plans much more predictable, as they no longer potentially have side effects on shared remote state.	10 years ago
Mitchell Hashimoto	f34ef1f92a	command: compilation works ... This still isn't ready. But this gets tests passing and compilation working	10 years ago
Mitchell Hashimoto	35c87836b4	core: Add terraform_version to state ... This adds a field terraform_version to the state that represents the Terraform version that wrote that state. If Terraform encounters a state written by a future version, it will error. You must use at least the version that wrote that state. Internally we have fields to override this behavior (StateFutureAllowed), but I chose not to expose them as CLI flags, since the user can just modify the state directly. This is tricky, but should be tricky to represent the horrible disaster that can happen by enabling it. We didn't have to bump the state format version since the absense of the field means it was written by version "0.0.0" which will always be older. In effect though this change will always apply to version 2 of the state since it appears in 0.7 which bumped the version for other purposes.	10 years ago
Paul Hinze	4a51e4fe91	core: write planfile even on empty plans ... This makes the planfile workflow more consistent. If a plan yields a noop, the apply of that planfile will noop. Fixes #1783	10 years ago
James Nugent	a49b162dd1	Prompt for input variables before context validate ... Also adds a regression test using Mock UI. Fixes #3767.	10 years ago
Anthony Scalisi	198e1a5186	remove various typos	11 years ago
Ryan Uber	9a091ffa78	command: plan supports detailed exit code	11 years ago
Mitchell Hashimoto	672bf58337	command: compiles, tests don't pass yet	12 years ago
Mitchell Hashimoto	91eb3c73fc	command: fix failing tests	12 years ago
Mitchell Hashimoto	15564b04a5	command: tests pass	12 years ago
Mitchell Hashimoto	9b2b3a963f	ResourceDiff => InstanceDiff	12 years ago
Mitchell Hashimoto	cdad3036ae	command: closer to compiling	12 years ago
Mitchell Hashimoto	642fed0356	command: terraform.tfvars loaded by default if it exists	12 years ago
Armon Dadgar	16ef3f5733	command: Testing the -backup feature	12 years ago
Mitchell Hashimoto	7b4119027a	command: -var-file works	12 years ago
Mitchell Hashimoto	3534470ca3	command: -var flag works	12 years ago
Mitchell Hashimoto	3a851bece0	command: convert all to use the new Meta thing	12 years ago
Mitchell Hashimoto	6bf543cb07	command/plan: default state path	12 years ago
Mitchell Hashimoto	04f7281e8c	command/plan: can take no args and default to pwd for config	12 years ago
Mitchell Hashimoto	d3d45ca064	command: fix some issues with refresh, tests passing	12 years ago
Mitchell Hashimoto	a6ae7230d1	command: use new API	12 years ago
Mitchell Hashimoto	64363da9dd	command/plan: add -destroy flag to plan a destroy	12 years ago
Mitchell Hashimoto	f820290862	command: -out flag to plan command	12 years ago
Mitchell Hashimoto	0a8cebdb82	command/plan: refresh by default	12 years ago
Mitchell Hashimoto	bff4b8a58c	command: plan	12 years ago