81 Commits (03f6c650ca9e78fc0d80d430ca1ec2a52c262da4)

Author	SHA1	Message	Date
James Bardin	07903189f1	s/Meta.lockState/Meta.stateLock/g	9 years ago
James Bardin	9cdba1f199	enable local state locking for apply ... Have the LocalBackend lock the state during operations, and enble this for the apply comand.	9 years ago
Mitchell Hashimoto	ad7b063262	command: convert to use backends	9 years ago
Mitchell Hashimoto	77efacf30e	command: use helper/variables for flags and parsing	9 years ago
Daniel Spangenberg	804a5bd3c5	Implements import with specified provider ... This allows the import with a specified provider. So far it was not possible to get resources imported from a different provider than the default.	9 years ago
Mitchell Hashimoto	251231e3ee	command: more manageable shadow error output	9 years ago
Mitchell Hashimoto	1a6056b287	command: split out and tag code so compilation works on Solaris ... The readline library doesn't support Solaris. For now, we'll just not support console there.	9 years ago
Mitchell Hashimoto	a867457d75	command/console	9 years ago
Mitchell Hashimoto	5107c33119	command/import: load configurations and allow empty config dirs ... Fixes #7774 This modifies the `import` command to load configuration files from the pwd. This also augments the configuration loading section for the CLI to have a new option (default false, same as old behavior) to allow directories with no Terraform configurations. For import, we allow directories with no Terraform configurations so this option is set to true.	9 years ago
Mitchell Hashimoto	57c0cadc79	Merge pull request #9666 from hashicorp/jbardin/debug ... preliminary debug output	9 years ago
Mitchell Hashimoto	f6dacab0ba	Merge pull request #9794 from hashicorp/b-partial-input ... command/meta: always ask for unset variable input	9 years ago
James Bardin	797a1b339d	DebugInfo and DebugGraph ... Implement debugInfo and the DebugGraph DebugInfo will be a global variable through which graph debug information can we written to a compressed archive. The DebugInfo methods are all safe for concurrent use, and noop with a nil receiver. The API outside of the terraform package will be to call SetDebugInfo to create the archive, and CloseDebugInfo() to properly close the file. Each write to the archive will be flushed and sync'ed individually, so in the event of a crash or a missing call to Close, the archive can still be recovered. The DebugGraph is a representation of a terraform Graph to be written to the debug archive, currently in dot format. The DebugGraph also contains an internal buffer with Printf and Write methods to add to this buffer. The buffer will be written to an accompanying file in the debug archive along with the graph. This also adds a GraphNodeDebugger interface. Any node implementing `NodeDebug() string` can output information to annotate the debug graph node, and add the data to the log. This interface may change or be removed to provide richer options for debugging graph nodes. The new graph builders all delegate the build to the BasicGraphBuilder. Having a Name field lets us differentiate the actual builder implementation in the debug graphs.	9 years ago
Mitchell Hashimoto	d429e82661	command: show shadow errors to the user	9 years ago
Mitchell Hashimoto	1248b147ac	command/meta: always ask for unset variable input ... Fixes #7975 This changes the InputMode for the CLI to always be: InputModeProvider | InputModeVar | InputModeVarUnset Which means: * Ask for provider variables * Ask for user variables _that are not already set_ The change is the latter point. Before, we'd only ask for variables if zero were given. This forces the user to either have no variables set via the CLI, env vars, tfvars or ALL variables, but no in between. As reported in #7975, this isn't expected behavior. The new change makes is so that unset variables are always asked for. Users can retain the previous behavior by setting `-input=false`. This would ensure that variables set by external sources cover all cases.	9 years ago
Mitchell Hashimoto	2019a44f04	command/apply: apply from plan respects -backup and -state-out ... Fixes #5409 I didn't expect this to be such a rabbit hole! Based on git history, it appears that for "historical reasons"(tm), setting up the various `state.State` structures for a plan were _completely different logic_ than a normal `terraform apply`. This meant that it was skipping things like disabling backups with `-backup="-"`. This PR unifies loading from a plan to the normal state setup mechanism. A few tests that were failing prior to this PR were added, no existing tests were changed.	9 years ago
Mitchell Hashimoto	af82be19ea	helper/experiment: a helper for setting, making experiments ... This creates a standard package and interface for defining, querying, setting experiments (`-X` flags). I expect we'll want to continue to introduce various features behind experimental flags. I want to make doing this as easy as possible and I want to make _removing_ experiments as easy as possible as well. The goal with this packge has been to rely on the compiler enforcing our experiment references as much as possible. This means that every experiment is a global variable that must be referenced directly, so when it is removed you'll get compiler errors where the experiment is referenced. This also unifies and makes it easy to grab CLI flags to enable/disable experiments as well as env vars! This way defining an experiment is just a couple lines of code (documented on the package).	9 years ago
Mitchell Hashimoto	1a418c1452	command/apply: -Xnew-destroy	9 years ago
Mitchell Hashimoto	ae4f79e3b6	command/meta: add -shadow flag to disable shadow graph ... Since it is still very much possible for this to cause problems, this can be used to disable the shadow graph. We'll purposely not document this since the goal is to remove this flag as we become more confident with it.	9 years ago
Mitchell Hashimoto	ec15783f24	-Xnew-apply to enable the new apply graph	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
James Nugent	681d94ae20	core: Allow lists and maps as variable overrides ... Terraform 0.7 introduces lists and maps as first-class values for variables, in addition to string values which were previously available. However, there was previously no way to override the default value of a list or map, and the functionality for overriding specific map keys was broken. Using the environment variable method for setting variable values, there was previously no way to give a variable a value of a list or map. These now support HCL for individual values - specifying: TF_VAR_test='["Hello", "World"]' will set the variable `test` to a two-element list containing "Hello" and "World". Specifying TF_VAR_test_map='{"Hello = "World", "Foo" = "bar"}' will set the variable `test_map` to a two-element map with keys "Hello" and "Foo", and values "World" and "bar" respectively. The same logic is applied to `-var` flags, and the file parsed by `-var-files` ("autoVariables"). Note that care must be taken to not run into shell expansion for `-var-` flags and environment variables. We also merge map keys where appropriate. The override syntax has changed (to be noted in CHANGELOG as a breaking change), so several tests needed their syntax updating from the old `amis.us-east-1 = "newValue"` style to `amis = "{ "us-east-1" = "newValue"}"` style as defined in TF-002. In order to continue supporting the `-var "foo=bar"` type of variable flag (which is not valid HCL), a special case error is checked after HCL parsing fails, and the old code path runs instead.	10 years ago
David Glasser	50959a654c	command: Remove second DefaultDataDirectory const (#7666)	10 years ago
James Nugent	5d18f41f04	core: Convert context vars to map[string]interface{} ... This is the first step in allowing overrides of map and list variables. We convert Context.variables to map[string]interface{} from map[string]string and fix up all the call sites.	10 years ago
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