508 Commits (a3c6fec4e69100738a165ac068b7ecbf54f785a3)

Author	SHA1	Message	Date
Mitchell Hashimoto	ab1e512ae2	command: use reset instead of reset_bold ... Fixes #10337 The `reset_bold` escape code (21) causes the text on Windows command prompts to just become invisible. `reset` does the same job for us in this scenario so do that.	9 years ago
Mitchell Hashimoto	28d933f6dd	nitpicks for #10310	9 years ago
Mitchell Hashimoto	c15754c365	Merge pull request #10310 from spangenberg/custom-import-provider ... Implements import with specified provider	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
James Bardin	bf20db688c	Remove extra dot from state backup file ... The state subcommand was adding an extra dot to the backup file	9 years ago
Mitchell Hashimoto	251231e3ee	command: more manageable shadow error output	9 years ago
James Bardin	b8adf10236	Add debug command with json2dot ... Add `terraform debug json2dot` to convert debug log graphs to dot format. This is not meant to be in place of more advanced debug visualization, but may continue to be a useful way to work with the debug output.	9 years ago
Mitchell Hashimoto	aaf1ad0532	Merge pull request #10093 from hashicorp/f-console ... Add `terraform console` for REPL	9 years ago
James Bardin	28d406c040	Provider a marshaler for dag.Graph ... The dot format generation was done with a mix of code from the terraform package and the dot package. Unify the dot generation code, and it into the dag package. Use an intermediate structure to allow a dag.Graph to marshal itself directly. This structure will be ablt to marshal directly to JSON, or be translated to dot format. This was we can record more information about the graph in the debug logs, and provide a way to translate those logged structures to dot, which is convenient for viewing the graphs.	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	785cc7b78a	terraform: default new graphs on, old graphs behind -Xlegacy-graph ... This turns the new graphs on by default and puts the old graphs behind a flag `-Xlegacy-graph`. This effectively inverts the current 0.7.x behavior with the new graphs. We've incubated most of these for a few weeks now. We've found issues and we've fixed them and we've been using these graphs internally for awhile without any major issue. Its time to default them on and get them part of a beta.	9 years ago
Mitchell Hashimoto	fd498fbfff	Merge pull request #9538 from hashicorp/f-nomad-provider ... provider/nomad: Nomad provider for managing jobs	9 years ago
Mitchell Hashimoto	f8ec7dad19	command/import: allow the -config flag to specify a config location	9 years ago
Mitchell Hashimoto	ec0ef95c6f	terraform: verify import providers only depend on vars	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	646b3c1b68	Merge pull request #9158 from hashicorp/f-vault-provider ... Vault Provider	9 years ago
Mitchell Hashimoto	57c0cadc79	Merge pull request #9666 from hashicorp/jbardin/debug ... preliminary debug output	10 years ago
Mitchell Hashimoto	f6dacab0ba	Merge pull request #9794 from hashicorp/b-partial-input ... command/meta: always ask for unset variable input	10 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.	10 years ago
Mitchell Hashimoto	d429e82661	command: show shadow errors to the user	10 years ago
Mitchell Hashimoto	6c801d0386	command/apply: add additional nil check to loading state for outputs	10 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.	10 years ago
Mitchell Hashimoto	ab0b7e2d89	Merge pull request #9660 from hashicorp/b-validate-help ... command/validate: respond to --help	10 years ago
Mitchell Hashimoto	314a8ed134	Merge pull request #9706 from hashicorp/b-apply-plan ... command/apply: apply from plan respects -backup and -state-out	10 years ago
Calle Pettersson	51ff5cba38	Align the help string of output with documentation (#9735)	10 years ago
Martin Atkins	b2b5831205	"vault" provider registration ... To reduce the risk of secret exposure via Terraform state and log output, we default to creating a relatively-short-lived token (20 minutes) such that Vault can, where possible, automatically revoke any retrieved secrets shortly after Terraform has finished running. This has some implications for usage of this provider that will be spelled out in more detail in the docs that will be added in a later commit, but the most significant implication is that a plan created by "terraform plan" that includes secrets leased from Vault must be *applied* before the lease period expires to ensure that the issued secrets remain valid. No resources yet. They will follow in subsequent commits.	10 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.	10 years ago
Mitchell Hashimoto	b2950bc205	command/validate: respond to --help ... Fixes #5072 This is very simple: we need to process CLI flags on validate in order to catch and respond to `--help`.	10 years ago
Mitchell Hashimoto	69b32223b8	Merge pull request #9633 from hashicorp/f-experiment ... helper/experiment: a helper for setting, making experiments	10 years ago
Mitchell Hashimoto	9c2014d5b6	Merge pull request #9642 from hashicorp/b-var-bool ... command: FlagTypedKV parses bool as string	10 years ago
Mitchell Hashimoto	f9b0207304	command: FlagTypedKV parses bool as string ... When passing a bool type to a variable such as `-var foo=true`, the CLI would parse this as a `bool` type which Terraform core cannot handle. It would then error with an invalid type error. This changes the handling to convert the bool to its literally string value given on the command-line.	10 years ago
James Bardin	43f860ddfd	Fix panic during "terraform show" with empty state ... It's possible to have > 1 result from the StateFilter, and not have any instances to show.	10 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).	10 years ago
Mitchell Hashimoto	aed23a0a31	Merge pull request #9527 from hashicorp/f-destroy-builder2 ... terraform: destroy graph builder based on state	10 years ago
Mitchell Hashimoto	bb5f6498e2	provider/nomad	10 years ago
Alexander Hellbom	d02067a75e	Add PagerDuty provider	10 years ago
Mitchell Hashimoto	1a418c1452	command/apply: -Xnew-destroy	10 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.	10 years ago
Mitchell Hashimoto	e8516f259d	command/apply: Xnew-apply	10 years ago
Mitchell Hashimoto	ec15783f24	-Xnew-apply to enable the new apply graph	10 years ago
James Bardin	f175497dd7	Fix vet issues ... None were critical, but these will fail with the next version of vet.	10 years ago
James Bardin	54d50c90b1	Make TestApply_parallelism more reliable ... Wait for our expected number of goroutines to be staged and ready, then allow Run() to complete. Use a high-water-mark counter to ensure we never exceeded the max expected concurrent goroutines at any point during the run.	10 years ago
James Bardin	4f91507d05	Merge pull request #9268 from hashicorp/jbardin/hcl-maps ... Get rid of the list when parsing HCL maps for vars	10 years ago
James Bardin	9fc50a76c3	Get rid of the list when parsing HCL maps for vars ... When we parse a map from HCL, it's decoded into a list of maps because HCL allows declaring a key multiple times to implicitly add it to a list. Since there's no terraform variable configuration that supports this structure, we can always flatten a []map[string]interface{} value to a map[string]interface{} and remove any type rrors trying to apply that value.	10 years ago
James Bardin	286fea571f	Fix push test to use something that is HCL ... Fix the tfvars push test which was mistakingly using a single number to trigger the HCL behavior.	10 years ago
James Bardin	cf1cfccf06	Don't parse a TestFlagTypedKV value as a number ... Don't try to parse a varibale as HCL if the value can be parse as a single number. HCL will always attempt to convert the value to a number, even if we later find the configured variable's type to be a string.	10 years ago
stack72	a2970e631c	Merge branch 'cwood/bitbucket-provider' of https://github.com/cwood/terraform into cwood-cwood/bitbucket-provider	10 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
Mitchell Hashimoto	fad1ce9915	Merge pull request #8620 from hashicorp/b-var-input ... command: more resilient HCL check for inputs	10 years ago