24 Commits (36cede09f7d8f664efdc542e41b147fa4108d0da)

Author	SHA1	Message	Date
Sander van Harmelen	7ec3f96e3a	command/state: update and fix the state mv command	8 years ago
Sander van Harmelen	536c2fe6f1	Make `state mv` use the new `states.Filter`	8 years ago
Martin Atkins	43d5206d82	command: Stub the "terraform state mv" tests to remind to fix ... This command isn't yet updated for the new state types, but since we were not returning a non-successful error status here the tests were just failing in a weird way instead. Now we'll fail with a message that makes it clear there is still work to do in the real implementation here.	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
James Bardin	55d18dcef2	update state rm amd mv docs ... Update the documentation to match the current behavior, and make the usage output and website docs match.	9 years ago
James Bardin	5b4ae36cb0	don't print help for state loading errors ... These already include detailed messages, and it's not a usage issue, it's a config or file location issue.	9 years ago
James Bardin	33ba6774e0	Make the state commands use the real command.Meta ... In order to use a backend for the state commands, we need an initialized meta. Use a single Meta instance rather than temporary ones to make sure the backends are initialized properly.	9 years ago
James Bardin	45a9edb763	make state mv and rm work with remote states ... The default value for the -state flag was overriding the location of any remote state.	9 years ago
Robert Liebowitz	006744bfe0	Use all tfvars files in working directory ... As a side effect, several commands that previously did not have a failure state can now fail during meta-parameter processing.	9 years ago
James Bardin	833cc9a6c5	Fix state mv/rm -backup documentation ... There is only one backup made, contrary to the help text. We may want to implement that, but the documentation should match the current behavior.	9 years ago
Edward Betts	be265479a9	correct spelling mistakes (#13979)	9 years ago
Mitchell Hashimoto	d2d87bccf0	Merge pull request #12155 from hashicorp/b-state-backend ... command: refresh state in old commands for backend	9 years ago
Mitchell Hashimoto	ebb22d3ecd	backend/local: don't RefreshState on State API	9 years ago
Mitchell Hashimoto	e4d2193ed6	command/state: mv and rm -backup works ... Fixes #12154 The "-backup" flag before for "state *" CLI had some REALLY bizarre behavior: it would change the _destination_ state and actually not create any additional backup at all (the original state was unchanged and the normal timestamped backup still are written). Really weird. This PR makes the -backup flag work as you'd expect with one caveat: we'll _still_ create the timestamped backup file. The timestamped backup file helps make sure that you always get a backup history when using these commands. We don't want to make it easy for you to overwrite a state with the `-backup` flag.	9 years ago
Mitchell Hashimoto	6e1dc9c77d	command: extra RefreshState calls	9 years ago
Mitchell Hashimoto	d3792e4aef	command: correct outdated comment	10 years ago
Mitchell Hashimoto	43cfd3d1c9	command: fix regressions for state mv with count resource	10 years ago
Mitchell Hashimoto	0d1ea84d39	command: test for moving resource with count [GH-7797]	10 years ago
Mitchell Hashimoto	3b3f92cd9b	terraform: fix some test failures on state add with multiple modules	10 years ago
James Nugent	aa5dc453ee	cli: Fix registration of `state mv`. ... Fixes #7259.	10 years ago
Mitchell Hashimoto	04598baa25	website: document state mv	10 years ago
Mitchell Hashimoto	c966a70ff9	command: update docs for state mv	10 years ago
Mitchell Hashimoto	235e860118	command/state mv: handle -state-out to a different path	10 years ago
Mitchell Hashimoto	c4e5355a02	command/state mv	10 years ago