87 Commits (3750bf7af220d91acbce3dde5ce4fba714c2db3b)

Author	SHA1	Message	Date
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	57c0cadc79	Merge pull request #9666 from hashicorp/jbardin/debug ... preliminary debug output	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	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	1a418c1452	command/apply: -Xnew-destroy	10 years ago
Mitchell Hashimoto	e8516f259d	command/apply: Xnew-apply	10 years ago
Radek Simko	8494cad8c4	Output 'destroy complete' when it's destroy (was: apply) (#8453)	10 years ago
James Nugent	0e4e94a86f	core: Fix -module for terraform output command ... The behaviour whereby outputs for a particular nested module can be output was broken by the changes for lists and maps. This commit restores the previous behaviour by passing the module path into the outputsAsString function. We also add a new test of this since the code path for indivdual output vs all outputs for a module has diverged.	10 years ago
James Nugent	3ea3c657b5	core: Use OutputState in JSON instead of map ... This commit forward ports the changes made for 0.6.17, in order to store the type and sensitive flag against outputs. It also refactors the logic of the import for V0 to V1 state, and fixes up the call sites of the new format for outputs in V2 state. Finally we fix up tests which did not previously set a state version where one is required.	10 years ago
James Nugent	6a20e8927d	core: Fix issues from rebasing dev-0.7 onto master ... - Fix sensitive outputs for lists and maps - Fix test prelude which was missed during conflict resolution - Fix `terraform output` to match old behaviour and not have outputs header and colouring - Bump timeout on TestAtlasClient_UnresolvableConflict	10 years ago
James Nugent	e57a399d71	core: Use native HIL maps instead of flatmaps ... This changes the representation of maps in the interpolator from the dotted flatmap form of a string variable named "var.variablename.key" per map element to use native HIL maps instead. This involves porting some of the interpolation functions in order to keep the tests green, and adding support for map outputs. There is one backwards incompatibility: as a result of an implementation detail of maps, one could access an indexed map variable using the syntax "${var.variablename.key}". This is no longer possible - instead HIL native syntax - "${var.variablename["key"]}" must be used. This was previously documented, (though not heavily used) so it must be noted as a backward compatibility issue for Terraform 0.7.	10 years ago
James Nugent	b62f6af158	core: Add support for marking outputs as sensitive (#6559) ... * core: Add support for marking outputs as sensitive This commit allows an output to be marked "sensitive", in which case the value is redacted in the post-refresh and post-apply list of outputs. For example, the configuration: ``` variable "input" { default = "Hello world" } output "notsensitive" { value = "${var.input}" } output "sensitive" { sensitive = true value = "${var.input}" } ``` Would result in the output: ``` terraform apply Apply complete! Resources: 0 added, 0 changed, 0 destroyed. Outputs: notsensitive = Hello world sensitive = <sensitive> ``` The `terraform output` command continues to display the value as before. Limitations: Note that sensitivity is not tracked internally, so if the output is interpolated in another module into a resource, the value will be displayed. The value is still present in the state.	10 years ago
David Glasser	b44f7f28e0	Document saved plan use in `terraform apply -help` (#6126) ... Wording borrowed from the website docs.	10 years ago
Jake Champlin	39e7f42490	Clear up `destroy --target` message ... When destroying infrastructure with `--target`, print out which infrastructure will be destroyed instead of saying `Terraform will delete all your managed infrastructure`. ``` terraform destroy --target aws_instance.test2 --target aws_instance.test1 Do you really want to destroy? Terraform will delete the following infrastructure: aws_instance.test2 aws_instance.test1 There is no undo. Only 'yes' will be accepted to confirm ``` Omitting `--target` arguments will use the default input description. ``` $ terraform destroy Do you really want to destroy? Terraform will delete all your managed infrastructure. There is no undo. Only 'yes' will be accepted to confirm. ```	10 years ago
Mitchell Hashimoto	344e7c26b5	fix a bunch of tests from go-getter import	11 years ago
Paul Hinze	374070d066	website: docs for parallelism setting ... /cc @stack72 @knuckolls @mitchellh	11 years ago
Paul Hinze	e1a46904d6	command: pull parallelism default up to CLI layer ... /cc @knuckolls @josephholsten	11 years ago
Kevin Nuckolls	f59c71b35a	works for apply, no tests yet	11 years ago
Anthony Scalisi	198e1a5186	remove various typos	11 years ago
Paul Hinze	ad680b1832	core: show outputs after `terraform refresh` ... closes #25	11 years ago
Paul Hinze	18924d24fe	command/apply: flatten multierrors ... Before: ``` Error applying plan: 1 error(s) occurred: * 1 error(s) occurred: * 1 error(s) occurred: * 1 error(s) occurred: * Error creating ... ``` After: ``` Error applying plan: 1 error(s) occurred: * Error creating ... ``` Muuuch better! :D	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	95cf69aa32	command: StateHook for continous state updates	11 years ago
Mitchell Hashimoto	fb3f10efb0	command/apply: ask for user variables before validation [GH-736]	11 years ago
Mitchell Hashimoto	90138825a2	command/apply: don't init if no args given [GH-780] ... I really don't know how to unit test this since I don't know what input triggers this except that it has been reporting a few times in the wild.	11 years ago
Armon Dadgar	0fb87e499d	command: Meta provides the state output path	11 years ago
Armon Dadgar	bf10111745	command/apply: Move state persistence to Meta	11 years ago
Armon Dadgar	5b745e5d46	command: Run validation before asking for input. Fixes #602	11 years ago
Panagiotis Moustafellos	3d51bae4b2	switch phrasing	12 years ago
Panagiotis Moustafellos	08515edc43	fixed typo on terraform destroy	12 years ago
Mitchell Hashimoto	8fc134caa1	command/destroy: don't show outputs	12 years ago
Mitchell Hashimoto	0914e17a2a	command/apply: more than one ctrl-c properly exits immediately	12 years ago
Mitchell Hashimoto	16b023bd2b	command: ask for the proper level of input	12 years ago
Mitchell Hashimoto	a5f70ead2d	command: destroy should ask for confirmation always	12 years ago
Mitchell Hashimoto	95f43d8230	command/apply: if with plan, don't ask for input [GH-346]	12 years ago
Mitchell Hashimoto	817f0d9f30	command: don't ask for input if terraform.tfvars file given [GH-346]	12 years ago
Mitchell Hashimoto	2131e4ffd2	command: fix failing tests	12 years ago
Mitchell Hashimoto	245c1ce05a	command: enable destroy	12 years ago
Mitchell Hashimoto	ab9dd71bcb	command/destroy: first steps	12 years ago
Mitchell Hashimoto	260c5301e6	command/apply: update usage	12 years ago
Mitchell Hashimoto	3572b8ff2f	command/apply: allow `terraform apply SOURCE` as shortcut for init	12 years ago
Mitchell Hashimoto	63453f3f1a	command: apply and refresh ask for input	12 years ago
Mitchell Hashimoto	ed538a9594	command: Get command, not functional yet. Converted to use modules.	12 years ago
Mitchell Hashimoto	cdad3036ae	command: closer to compiling	12 years ago
AJ Bourg	aefa4b2399	expacts -> expects. (minor)	12 years ago
Alex Gaynor	46154ca1d3	Fixed a ton of typos in docs and comments	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