94 Commits (28543694de6333696f07e1008153a6c0d2811983)

Author	SHA1	Message	Date
Paul Hinze	b0485db5f4	website: Remove `-backup` from `plan` docs ... Refs #7087	10 years ago
Devon Harvey	689cfc97c1	Fix typo in show command docs (#6784)	10 years ago
Mitchell Hashimoto	54df833406	website: add import command docs	10 years ago
Mitchell Hashimoto	9ddf73ad81	website: update docs	10 years ago
Mitchell Hashimoto	04598baa25	website: document state mv	10 years ago
Mitchell Hashimoto	473a58a672	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
Mitchell Hashimoto	e133452663	command/state: pattern => address	10 years ago
Mitchell Hashimoto	5737c0a13b	website: update docs for state show	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
Dan Carley	64c1280951	command/fmt: Improve documentation for -diff and defaults (#6398) ... * command/fmt: Document -diff doesn't disable -write As noted in hashicorp/terraform#6343, this description misleadingly suggested that the `-diff` option disables the `-write` option. This isn't the case and because of the default options (described in c753390) the behaviour of `terraform fmt -diff` is actually the same as `terraform fmt -write -list -diff`. Replace the "instead of rewriting" description to clarify that. Documentation in hcl/fmtcmd is corrected in hashicorp/hcl#117 but it's not really necessary to bump the dependency version. * command/fmt: Show flag defaults in help text These were documented on the website but not in the `-help` text. This should help to clarify that you need to pass `-list=false -write=false -diff` if you only want to see diffs. Accordingly I've replaced the word "disabled" with "always false" in the STDIN special cases so that it matches the terminology used in the defaults and better indicates that it is overridden. NB: The 3x duplicated defaults and documentation makes me feel uneasy once again. I'm not sure how to solve that, though.	10 years ago
Martin Atkins	fa703db8a6	Merge #4955: "terraform fmt" command	10 years ago
Paul Hinze	c7f5450a96	command: Add `terraform untaint` ... - [x] Docs - [x] Command Unit Tests - [x] State Unit Tests Closes #4820	10 years ago
Dan Carley	79e2753e41	command/fmt: Disable list/write when using STDIN ... These options don't make sense when passing STDIN. `-write` will raise an error because there is no file to write to. `-list` will always say `<standard input>`. So disable whenever using STDIN, making the command much simpler: cat main.tf | terraform fmt -	10 years ago
Dan Carley	e9128769b5	command/fmt: Accept input from STDIN ... So that you can do automatic formatting from an editor. You probably want to disable the `-write` and `-list` options so that you just get the re-formatted content, e.g. cat main.tf | terraform fmt -write=false -list=false - I've added a non-exported field called `input` so that we can override this for the tests. If not specified, like in `commands.go`, then it will default to `os.Stdin` which works on the command line.	10 years ago
Dan Carley	1b967e612f	command/fmt: Accept optional directory argument ... So that you can operate on files in a directory other than your current working directory.	10 years ago
Dan Carley	c753390399	command/fmt: Default write and list to true ... The most common usage usage will be enabling the `-write` and `-list` options so that files are updated in place and a list of any modified files is printed. This matches the default behaviour of `go fmt` (not `gofmt`). So enable these options by default. This does mean that you will have to explicitly disable these if you want to generate valid patches, e.g. `terraform fmt -diff -write=false -list=false`	10 years ago
Dan Carley	cc41c7cfa0	command/fmt: Add new fmt command ... This uses the `fmtcmd` package which has recently been merged into HCL. Per the usage text, this rewrites Terraform config files to their canonical formatting and style. Some notes about the implementation for this initial commit: - all of the fmtcmd options are exposed as CLI flags - it operates on all files that have a `.tf` suffix - it currently only operates on the working directory and doesn't accept a directory argument, but I'll extend this in subsequent commits - output is proxied through `cli.UiWriter` so that we write in the same way as other commands and we can capture the output during tests - the test uses a very simple fixture just to ensure that it is working correctly end-to-end; the fmtcmd package has more exhaustive tests - we have to write the fixture to a file in a temporary directory because it will be modified and for this reason it was easier to define the fixture contents as a raw string	10 years ago
gamename	3bc09db7e0	docs(variables): redundant wording	10 years ago
gamename	c6b350b98e	docs(variables): describe order of evaluation with files	10 years ago
Radek Simko	7fed07a0a2	docs: Clarify use cases in docs for the validate cmd	10 years ago
Soren Mathiasen	db69a2959b	Added verify command	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
Radek Simko	f2ffff33eb	docs: Create new section for remote state backends	10 years ago
Seth Vargo	ef30df002a	Fix broken link	10 years ago
Seth Vargo	8dbc43639d	Use HTTPS + www. for links	10 years ago
John E. Vincent	0e664c8c20	making note of artifactory env vars that are supported	10 years ago
Sander van Harmelen	9b27db6fea	Add the option to specify a custom (AWS compatible) S3 endpoint ... Same fix/option as I added in Vault not too long ago: https://github.com/hashicorp/vault/pull/750	10 years ago
James Nugent	562b7dfab7	Add documentation for Artifactory remote state	10 years ago
Paul Hinze	1a19f43ee1	core: support HTTP basic auth in consul remote state ... Closes #1663	10 years ago
Chad Thompson	d309f8b82b	Update remote-config.html.markdown ... Replace "shared storaged" with "shared storage". (Very minor change.)	10 years ago
Martin Atkins	484d6f8765	Merge pull request #3487 from nathan7/etcd ... Etcd remote state backend	11 years ago
David Adams	3021069207	Update init and remote config command docs ... * Update init docs to be correct, and provide an example. * Update remote config docs to provide more details about the Consul backend and to provide another example.	11 years ago
Nathan Zadoks	362a2035c0	Document the etcd remote state backend	11 years ago
Julian C. Dunn	3143d1703d	Graphviz Workspace appears to be dead, so remove it from the docs.	11 years ago
Paul Hinze	374070d066	website: docs for parallelism setting ... /cc @stack72 @knuckolls @mitchellh	11 years ago
Radek Simko	4f7f20ba23	remote/s3: Add some docs for supported parameters	11 years ago
Anthony Scalisi	198e1a5186	remove various typos	11 years ago
Radek Simko	3f7c3a92c3	docs: Fix typo (hyphen -> underscore) in remote-config	11 years ago
Radek Simko	5560f8a8d2	Merge pull request #3057 from jszwedko/patch-1 ... Fix remote state AWS configuration key names	11 years ago
Mark Turner	c9ec10d71a	Altered Consul variable from 'access-token' to 'access_token' so it's the same as in the codebase	11 years ago
Jesse Szwedko	43e6a14290	Fix remote state AWS configuration key names	11 years ago
Mitchell Hashimoto	3cc5252b9d	website: update copy	11 years ago
Mitchell Hashimoto	9d9bcc2f6e	command/push: update flag to -overwrite, update docs	11 years ago
Mitchell Hashimoto	82028a7667	website: update push docs	11 years ago
Paul Hinze	a75095aa69	docs: clarify wording around destroy/apply args ... inspired by #2360 with clarification on args vs flags /cc @catsby	11 years ago
Kirill Shirinkin	b945d1ee0b	Update docs	11 years ago
Paul Hinze	d30d88e327	Merge pull request #1655 from hashicorp/f-build-graph-during-plan ... core: validate on verbose graph to detect some cycles earlier	11 years ago
Martin Atkins	53e93d6f63	S3 remote stage storage backend, against the new remote state API. ... Stores state in a particular key in a given S3 bucket.	11 years ago
Paul Hinze	ce49dd6080	core: graph command gets -verbose and -draw-cycles ... When you specify `-verbose` you'll get the whole graph of operations, which gives a better idea of the operations terraform performs and in what order. The DOT graph is now generated with a small internal library instead of simple string building. This allows us to ensure the graph generation is as consistent as possible, among other benefits. We set `newrank = true` in the graph, which I've found does just as good a job organizing things visually as manually attempting to rank the nodes based on depth. This also fixes `-module-depth`, which was broken post-AST refector. Modules are now expanded into subgraphs with labels and borders. We have yet to regain the plan graphing functionality, so I removed that from the docs for now. Finally, if `-draw-cycles` is added, extra colored edges will be drawn to indicate the path of any cycles detected in the graph. A notable implementation change included here is that {Reverse,}DepthFirstWalk has been made deterministic. (Before it was dependent on `map` ordering.) This turned out to be unnecessary to gain determinism in the final DOT-level implementation, but it seemed a desirable enough of a property that I left it in.	11 years ago
Mitchell Hashimoto	c9fe0c1b34	website: fix remote config docs	11 years ago