8 Commits (00a76d019a3e5b4d9d040a3e28c9e0b4e56ad951)

Author	SHA1	Message	Date
James Bardin	f375691819	add missing key-value from test	8 years ago
Sander van Harmelen	af1a471a05	command/state: update and fix the state list command	8 years ago
Martin Atkins	d48f3600fe	states: In Module.testString, use incrementing ids for deposed ... In our old world we always used 1-based indices into a slice of deposed objects. The new models instead use a map keyed by pseudorandom strings, so that deposed objects will have a consistent identity across multiple operations. However, having that pseudo-random string in our test comparison output is not helpful, since such strings can never match hard-coded expectation strings. Therefore for the purposes of generating this test comparison output we'll revert back to using 1-based indexes. This should avoid problems for tests that only create one deposed object per instance, but those which create more than one will need to do some more work since the _ordering_ of these objects in the output is still pseudorandom as a result of it coming from a map rather than a slice.	8 years ago
Martin Atkins	83066cd57f	states: Support non-string primitives in state string representation	8 years ago
Martin Atkins	5faf027ea7	states: In State.String, use colon suffix only after all module names	8 years ago
James Bardin	6f429cc81b	make state output match legacy output	8 years ago
Martin Atkins	a3403f2766	terraform: Ugly huge change to weave in new State and Plan types ... Due to how often the state and plan types are referenced throughout Terraform, there isn't a great way to switch them out gradually. As a consequence, this huge commit gets us from the old world to a _compilable_ new world, but still has a large number of known test failures due to key functionality being stubbed out. The stubs here are for anything that interacts with providers, since we now need to do the follow-up work to similarly replace the old terraform.ResourceProvider interface with its replacement in the new "providers" package. That work, along with work to fix the remaining failing tests, will follow in subsequent commits. The aim here was to replace all references to terraform.State and its downstream types with states.State, terraform.Plan with plans.Plan, state.State with statemgr.State, and switch to the new implementations of the state and plan file formats. However, due to the number of times those types are used, this also ended up affecting numerous other parts of core such as terraform.Hook, the backend.Backend interface, and most of the CLI commands. Just as with 5861dbf3fc before, I apologize in advance to the person who inevitably just found this huge commit while spelunking through the commit history.	8 years ago
Martin Atkins	cf6892275a	states: Port stringer implementation from terraform.State ... Our existing core tests make extensive use of the string representation of a state for comparison purposes, because they were written before we began making use of helper packages like "cmp". To avoid the need to rewrite all of those tests and potentially break them, we will instead port that particular rendering as closely as possible but mark it with a comment sternly warning not to use it for anything new. We don't want to use this moving forward for a number of reasons, but most notably: - printing out whole before and after state representations makes it hard to find a subtle difference in outcome when a test fails, while "cmp" can provide us with a real diff. - this string serialization is constrained by the capabilities of Terraform prior to our new state models, and so it does not comprehensively represent all possibilities in the new world. - it will probably behave oddly/poorly when given states containing features that arrived after it was written, even though I made a best effort here to make it do something reasonable in situations I thought about.	8 years ago