58 Commits (28543694de6333696f07e1008153a6c0d2811983)

Author	SHA1	Message	Date
James Bardin	6b5ee73e86	Use -state-out option when applying from a plan ... When working from an existing plan, we weren't setting the PathOut field for a LocalState. This required adding an outPath argument to the StateFromPlan function to avoid having to introspect the returned state.State interface to find the appropriate field. To test we run a plan first and provide the new plan to apply with `-state-out` set.	10 years ago
Mitchell Hashimoto	3c9a92e04a	command: Context buliding allows empty module trees	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
Mitchell Hashimoto	d1b46e99bd	Add `terraform state list` command ... This introduces the terraform state list command to list the resources within a state. This is the first of many state management commands to come into 0.7. This is the first command of many to come that is considered a "plumbing" command within Terraform (see "plumbing vs porcelain": http://git.661346.n2.nabble.com/what-are-plumbing-and-porcelain-td2190639.html). As such, this PR also introduces a bunch of groundwork to support plumbing commands. The main changes: - Main command output is changed to split "common" and "uncommon" commands. - mitchellh/cli is updated to support nested subcommands, since terraform state list is a nested subcommand. - terraform.StateFilter is introduced as a way in core to filter/search the state files. This is very basic currently but I expect to make it more advanced as time goes on. - terraform state list command is introduced to list resources in a state. This can take a series of arguments to filter this down. Known issues, or things that aren't done in this PR on purpose: - Unit tests for terraform state list are on the way. Unit tests for the core changes are all there.	10 years ago
Paul Hinze	e67fc0fe9b	command: Change module-depth default to -1 ... This means that terraform commands like `plan`, `apply`, `show`, and `graph` will expand all modules by default. While modules-as-black-boxes is still very true in the conceptual design of modules, feedback on this behavior has consistently suggested that users would prefer to see more verbose output by default. The `-module-depth` flag and env var are retained to allow output to be optionally limited / summarized by these commands.	10 years ago
Mitchell Hashimoto	344e7c26b5	fix a bunch of tests from go-getter import	11 years ago
Kevin Nuckolls	f59c71b35a	works for apply, no tests yet	11 years ago
Anthony Scalisi	198e1a5186	remove various typos	11 years ago
Mitchell Hashimoto	96b53cc06c	command: ask for input even if tfvars is set [GH-2161]	11 years ago
Radek Simko	cdcd11419e	Add -no-color option for subcommands	11 years ago
Paul Hinze	29d34cd5a4	command: allow module depth to be set via env var ... Another convienence env var here with TF_MODULE_DEPTH. Works like you'd expect it to!	11 years ago
Paul Hinze	5f1ea7fccc	command: add env var equivalent to -input arg ... Setting TF_INPUT has the equivalent effect of setting the flag. I got sick of specifying this when iterating on TF config locally.	11 years ago
Paul Hinze	97acccd3ed	core: targeted operations ... Add `-target=resource` flag to core operations, allowing users to target specific resources in their infrastructure. When `-target` is used, the operation will only apply to that resource and its dependencies. The calculated dependencies are different depending on whether we're running a normal operation or a `terraform destroy`. Generally, "dependencies" refers to ancestors: resources falling _before_ the target in the graph, because their changes are required to accurately act on the target. For destroys, "dependencies" are descendents: those resources which fall _after_ the target. These resources depend on our target, which is going to be destroyed, so they should also be destroyed.	11 years ago
Mitchell Hashimoto	eebd7b8aa3	command/push: ask for only variables that are unset	11 years ago
Mitchell Hashimoto	c4dc9af120	command: add DataDir	11 years ago
Paul Hinze	4fc5ebf47e	command: warnings should not exit ... also properly colorize error/warnings depends on https://github.com/mitchellh/cli/pull/15	11 years ago
Mitchell Hashimoto	71315076c3	command: autoload terraform.tfvars.json as well [GH-1030]	11 years ago
Mitchell Hashimoto	2c2b560d7f	command/remote: no more remote package	11 years ago
Mitchell Hashimoto	3550f7ac3a	command: FlagVar => FlagKV	11 years ago
Mitchell Hashimoto	4f91b98a3e	command: default path should be the local path	11 years ago
Mitchell Hashimoto	f81110c2fe	command: backup stuff works better	11 years ago
Mitchell Hashimoto	4ec63bc2ef	command: deal with plan states	11 years ago
Mitchell Hashimoto	579f102f37	command: start migrating to new state package	11 years ago
Armon Dadgar	b69239e7f8	command/meta: Adding additional nil guards	11 years ago
Armon Dadgar	408ae62306	command/apply: Handle remote state in a plan file	11 years ago
Armon Dadgar	ba01e27026	command: Refresh remote state when loading	11 years ago
Armon Dadgar	0fb87e499d	command: Meta provides the state output path	11 years ago
Armon Dadgar	53704db4ee	command: Enable reading remote-enabled state	11 years ago
Armon Dadgar	bf10111745	command/apply: Move state persistence to Meta	11 years ago
Mitchell Hashimoto	5f6fe1f931	command: put the modules in ".terraform/modules" ... This also fixes a case where tests wre leaking files	12 years ago
Mitchell Hashimoto	16b023bd2b	command: ask for the proper level of input	12 years ago
Mitchell Hashimoto	817f0d9f30	command: don't ask for input if terraform.tfvars file given [GH-346]	12 years ago
Mitchell Hashimoto	245c1ce05a	command: enable destroy	12 years ago
Mitchell Hashimoto	901c1448b4	command: make the UI a look nicer	12 years ago
Mitchell Hashimoto	af548c9b53	command/plan: ask for input	12 years ago
Mitchell Hashimoto	5b0859b3f5	command: Input tells us whether we should ask for input or not	12 years ago
Mitchell Hashimoto	672bf58337	command: compiles, tests don't pass yet	12 years ago
Mitchell Hashimoto	1b8426f7ff	command: Get works	12 years ago
Mitchell Hashimoto	ed538a9594	command: Get command, not functional yet. Converted to use modules.	12 years ago
Mitchell Hashimoto	b5daa2f41e	command: make the default var-file flag easier	12 years ago
Mitchell Hashimoto	546865e1ee	command: make sure errors from flag go to UI [GH-269]	12 years ago
Mitchell Hashimoto	69294b1ba3	command: adhere to -no-color, fix test [GH-250]	12 years ago
Mitchell Hashimoto	2caf33f97f	command/apply: keep track of default variables separately [GH-153]	12 years ago
Mitchell Hashimoto	bc1947124e	command: fix data race on Ui	12 years ago
Mitchell Hashimoto	642fed0356	command: terraform.tfvars loaded by default if it exists	12 years ago
Mitchell Hashimoto	b172f45b94	command: make state unexported on Meta	12 years ago
Armon Dadgar	54cc66367d	command: Adding backup of state file	12 years ago
Mitchell Hashimoto	ef6fba754d	command: refactor so Context never plans	12 years ago
Mitchell Hashimoto	82e7d58250	command/apply: -init is gone ... /cc @pearkes - hurray!	12 years ago
Mitchell Hashimoto	79033f240f	command: error if variables present when creating context from plan	12 years ago