terraform

Commit Graph

Author	SHA1	Message	Date
Laura Pacilio	8525befc22	Add description metadata to index page	5 years ago
ritsok	595646916f	Link refresh tutorial from plan and refresh docs pages	5 years ago
Adrian	54a09b059f	error_count # shouldn't it be true if the error count is zero error_count (number): A zero or positive whole number giving the count of errors Terraform detected. If valid is 'true' then error_count will always be zero, because it is the presence of errors that indicates that a configuration is invalid.	5 years ago
Alisdair McDiarmid	32210db0ab	documentation: Add drift to machine readable UI	5 years ago
Laura Pacilio	577c3653f2	Merge pull request #28983 from KurtLehnardt/patch-1 fixed typo	5 years ago
Laura Pacilio	a7e24c384b	Merge pull request #28842 from iaoiui/patch-1 remove extra "be"	5 years ago
Laura Pacilio	f9ec36383d	Merge pull request #29011 from vlad-ro/patch-1 Add back missing closing quote character	5 years ago
Laura Pacilio	4f12b8d917	Merge pull request #28863 from stensonb/patch-1 typo	5 years ago
Laura Pacilio	de97a03528	Merge pull request #28908 from kondr57/patch-1 fix typo	5 years ago
Martin Atkins	a945b379d8	website: Explicit examples of -var escaping in various shells The -var command line option comes with the disadvantage that a user must contend both with Terraform's own parser and with the parser in whichever shell they've decided to use, and different shells on different platforms have different rules. Previously we've largely just assumed that folks know the appropriate syntax for the shell they chose, but it seems that command lines involving spaces and other special characters arise rarely enough in other commands that Terraform is often the first time someone needs to learn the appropriate syntax for their shell. We can't possibly capture all of the details of all shells in our docs, because that's far outside of our own scope, but hopefully this new section will go some way to give some real examples that will help folks figure out how to write suitable escape sequences, if they choose to set complex variable values on the command line rather than in .tfvars as we recommend elsewhere on this page.	5 years ago
Robin Norwood	50fe980877	Merge pull request #28998 from hashicorp/rln-add-versions-tutorials-links Add links to terraform versions tutorials	5 years ago
Vlad Romanenko	d4d56a96b1	Add back missing closing quote character	5 years ago
Robin Norwood	2c71bb3a2e	Add links to terraform versions tutorials	5 years ago
Radek Simko	bb868606ea	docs: Document naming conventions for templates & backend configs (#28924 ) * docs: Document naming conventions for templates & backend configs * Update website/docs/cli/config/config-file.html.md Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com> * Update website/docs/language/functions/templatefile.html.md Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com> Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	5 years ago
Kurt Lehnardt	165b2a2509	fixed typo	5 years ago
Kristin Laemmert	583859e510	commands: `terraform add` (#28874 ) * command: new command, terraform add, generates resource templates terraform add ADDRESS generates a resource configuration template with all required (and optionally optional) attributes set to null. This can optionally also pre-populate nonsesitive attributes with values from an existing resource of the same type in state (sensitive vals will be populated with null and a comment indicating sensitivity) * website: terraform add documentation	5 years ago
Kristin Laemmert	ac03d35997	jsonplan and jsonstate: include sensitive_values in state representations (#28889 ) * jsonplan and jsonstate: include sensitive_values in state representations A sensitive_values field has been added to the resource in state and planned values which is a map of all sensitive attributes with the values set to true. It wasn't entirely clear to me if the values in state would suffice, or if we also need to consult the schema - I believe that this is sufficient for state files written since v0.15, and if that's incorrect or insufficient, I'll add in the provider schema check as well. I also updated the documentation, and, since we've considered this before, bumped the FormatVersions for both jsonstate and jsonplan.	5 years ago
Kristin Laemmert	9ca3cb4233	website/docs: move type func docs to a useful location (#28940 ) * website/docs: move type func docs to a useful location * docs don't exist if you don't put them in the index (again)	5 years ago
Vladimir Kondratiev	58a5207dc4	fix typo	5 years ago
Martin Atkins	f52aec8e3d	website: Fix formatting of v1 compatibility promises Seems like we lost a newline in some of the shuffling it took to get this into the live website, and so it's formatting oddly in the rendered website. This restores the intended formatting of this as the start of a bullet list, rather than as a continuation of the previous paragraph.	5 years ago
Judith Malnick	044c439dbc	Gloss of top docs pages (#28891 ) * clarify input variables opening sentence * adjust variables description * claraify providers text and add learn callout * add description to providers page * add desscription and clarify provider configuration * add deprecation note to versions in proivder configs * add hands on callout and clarify next steps in intro * link to language collection from language docs * give more context about configurtion language up front * clarify output top page * reorganize for each intro to present feature before notes * move description before link out and remove passive voice * fix typo * clarify purpose of plan * move explanation before learn link and fully spell boolean * add a syntax heading to separate intro from details * add learn callout to module source docs * clean up intro to provider requirements and add link * Apply suggestions from code review Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Martin Atkins	07aa07f5b9	website: First Draft of Upgrade Guide	5 years ago
Bryan Stenson	b487b9f8fb	typo	5 years ago
iaoiui	176cfad1dd	remove extra "be"	5 years ago
Judith Malnick	d7f6000118	Revert "mclarify specifying provider versions" This reverts commit `397494daca`.	5 years ago
Judith Malnick	397494daca	mclarify specifying provider versions	5 years ago
Martin Atkins	4e74a7a4f1	initwd: Error message for local paths escaping module packages Our module installer has a somewhat-informal idea of a "module package", which is some external thing we can go fetch in order to add one or more modules to the current configuration. Our documentation doesn't talk much about it because most users seem to have found the distinction between external and local modules pretty intuitive without us throwing a lot of funny terminology at them, but there are some situations where the distinction between a module and a module package are material to the end-user. One such situation is when using an absolute rather than relative filesystem path: we treat that as an external package in order to make the resulting working directory theoretically "portable" (although users can do various other things to defeat that), and so Terraform will copy the directory into .terraform/modules in the same way as it would download and extract a remote archive package or clone a git repository. A consequence of this, though, is that any relative paths called from inside a module loaded from an absolute path will fail if they try to traverse upward into the parent directory, because at runtime we're actually running from a copy of the directory that's been taking out of its original context. A similar sort of situation can occur in a truly remote module package if the author accidentally writes a "../" source path that traverses up out of the package root, and so this commit introduces a special error message for both situations that tries to be a bit clearer about there being a package boundary and use that to explain why installation failed. We would ideally have made escaping local references like that illegal in the first place, but sadly we did not and so when we rebuilt the module installer for Terraform v0.12 we ended up keeping the previous behavior of just trying it and letting it succeed if there happened to somehow be a matching directory at the given path, in order to remain compatible with situations that had worked by coincidence rather than intention. For that same reason, I've implemented this as a replacement error message we will return only if local module installation was going to fail anyway, and thus it only modifies the error message for some existing error situations rather than introducing new error situations. This also includes some light updates to the documentation to say a little more about how Terraform treats absolute paths, though aiming not to get too much into the weeds about module packages since it's something that most users can get away with never knowing.	5 years ago
Martin Atkins	abf7f3416b	website: "taint" command is deprecated from v0.15.2, not from v1.0.0 We got the replacement for this in earlier than anticipated, so these docs were originally more pessimistic about when the alternative would be available.	5 years ago
Martin Atkins	6d80088f51	website: More accurate release versions for new plan options While we were working on and documenting these it wasn't clear exactly what Terraform CLI version they would land in, and so we used "Terraform v1.0" in the docs as a safe bound that was definitely going to include all of them. With everything now landed though, we can be more specific about which v0.15.x minor release each of these appeared in.	5 years ago
Alisdair McDiarmid	f9fc47c22e	website: Add documentation for machine readable UI Terraform 0.15.3 added support for a `-json` flag to the plan, apply, and refresh commands, which renders the Terraform UI output in a structured machine readable format. This commit adds documentation for this interface.	5 years ago
Matthew Sanabria	1c3f4fe80f	Add examples to `terraform console` command (#28773 ) These examples showcase come use cases for `terraform console`.	5 years ago
Matthew Sanabria	a63ac81d0c	Example plugin location using XDG Base Directory (#28711 ) The current documention was unclear about the full path of local mirrors when using the XDG Base Directory Specification. Also removed the trailing slashes for the other paths in this section.	5 years ago
James Bardin	65ee33a90d	Merge pull request #28748 from Bredoxon/patch-1 Fix typo in the docs	5 years ago
Bredoxon	06e756eb0c	Fix typo in the docs	5 years ago
James Bardin	760a59b3a7	negative substring	5 years ago
Karol Szczepański	f684f91f3f	website/docs(plan): fix minor typos (#28713 )	5 years ago
Kyle A. Matheny	3afa08b1bc	Remove duplicate word (#28716 )	5 years ago
James Bardin	51a171c7f4	pg requires PostgreSQL 10	5 years ago
James Bardin	1b48636b42	update init docs for -migrate-state	5 years ago
Nick Fagerlund	65f3ddec52	website: Make apply's usage of plan options harder to miss - I'm using distinct subheaders and smaller paragraphs to try and make the info about apply's two modes more skimmable. - I'm also adding a separate "Plan Options" subheader (and keeping the section tiny so it stays snugged up right next to the "Apply Options" one) to make it extra-clear that Hey, There's More Options, They're Over There.	5 years ago
Alisdair McDiarmid	3e40a9a4eb	Merge pull request #28507 from stevematney/patch-1 Updating sensitive/nonsensitive docs with v0.14 specifics.	5 years ago
Steve Matney	e27a927ba4	Updating sensitive and nonsensitive docs with correct v0.15 info.	5 years ago
Martin Atkins	3c8a4e6e05	command+backend/local: -refresh-only and drift detection This is a light revamp of our plan output to make use of Terraform core's new ability to report both the previous run state and the refreshed state, allowing us to explicitly report changes made outside of Terraform. Because whether a plan has "changes" or not is no longer such a straightforward matter, this now merges views.Operation.Plan with views.Operation.PlanNoChanges to produce a single function that knows how to report all of the various permutations. This was also an opportunity to fill some holes in our previous logic which caused it to produce some confusing messages, including a new tailored message for when "terraform destroy" detects that nothing needs to be destroyed. This also allows users to request the refresh-only planning mode using a new -refresh-only command line option. In that case, Terraform _only_ performs drift detection, and so applying a refresh-only plan only involves writing a new state snapshot, without changing any real infrastructure objects.	5 years ago
Martin Atkins	42e0985839	command: use -lock=false consistently in -help output Previously the docs for this were rather confusing because they showed an option to turn _on_ state locking, even though it's on by default. Instead, we'll now show -lock=false in all cases and document it as _disabling_ the default locking. While working on this I also noticed that the equivalent docs on the website were differently inconsistent. I've not made them fully consistent here but at least moreso than they were before.	5 years ago
Martin Atkins	ed121321c6	website: Revamp the "terraform state mv" page My original motivation here was to add the previously-missing -dry-run option to the list of options However, while in the area I noticed that this command hasn't had a documentation refresh for a while and so I took the opportunity to update it to match with our current writing style and terminology used in other parts of the documentation, and so I've rewritten prose elsewhere on the page to hopefully give the same information in a way that fits in better with concepts discussed elsewhere in the documentation, and also to try to add some additional context to connect this information with what we've described in other places. This rewrite also drops the example of moving from one "state file" to another, because that's a legacy usage pattern that isn't supported when using remote backends, and we recommend most folks to use remote backends so it's strange to show an example that therefore won't work for most people. Rather than adding additional qualifiers to that example I chose to just remove it altogether, because we've generally been working to de-emphasize these legacy local backend command line options elsewhere in the documentation.	5 years ago
Martin Atkins	ea089d06f1	website: Revamp the "terraform state rm" page My original motivation here was to add the previously-missing -dry-run option to the list of options However, while in the area I noticed that this command hasn't had a documentation refresh for a while and so I took the opportunity to update it to match with our current writing style and terminology used in other parts of the documentation, and so I've rewritten prose elsewhere on the page to hopefully give the same information in a way that fits in better with concepts discussed elsewhere in the documentation, and also to try to add some additional context to connect this information with what we've described in other places.	5 years ago
Martin Atkins	0aa0e00fdc	website: Backend docs link to new .gitignore anchor The Git book seems to be using a different anchor format now, and so this link was previously effectively linking to the page as a whole rather than to the specific section we're trying to refer to.	5 years ago
Martin Atkins	874f1abb2b	cli+website: -ignore-remote-version docs and other cleanup We previously had only very short descriptions of what -ignore-remote-version does due to having the documentation for it inline on many different command pages and -help output. Instead, we'll now centralize the documentation about this argument on the remote backend page, and link to it or refer to it from all other locations. This then allows us to spend more words on discussing what Terraform normally does _without_ this option and warning about the consequences of using it. This continues earlier precedent for some local-backend-specific options which we also don't recommend for typical use. While this does make these options a little more "buried" than before, that feels justified given that they are all "exceptional use only" sort of options where users ought to learn about various caveats before using them. While there I also took this opportunity to fix some earlier omissions with the local-backend-specific options and a few other minor consistency tweaks.	5 years ago
Roger Berlind	b6885923d0	website: Add link to Modules in Package Sub-directories (#27980 ) * Add link to Modules in Package Sub-directories Add link to "Modules in Package Sub-directories" section at top of page * Fix broken links * Update aws link, fixes missing anchor linkcheck Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Martin Atkins	6f68065326	website: Explicit example of for_each chaining between resources This pattern follows as a natural consequence of how for_each is defined, but I've noticed from community forum Q&A that newcomers often don't immediately notice the connection between what for_each expects as input and what a for_each resource produces as a result, so my aim here is to show a short example of that in the hope of helping folks see the link here and get ideas on how to employ the technique in other situations.	5 years ago
Rachel Sharp	87c9e78666	Merge pull request #28604 from hashicorp/res-lifecycle-tutorial Add link to lifecycle tutorial	5 years ago
Alisdair McDiarmid	a5b7394f9a	command/jsonplan: Add replace_paths The set of paths which caused a resource update to require replacement has been stored in the plan since 0.15.0 (#28201). This commit adds a simple JSON representation of these paths, allowing consumers of this format to determine exactly which paths caused the resource to be replaced. This representation is intentionally more loosely encoded than the JSON state serialization of paths used for sensitive attributes. Instead of a path step being represented by an object with type and value, we use a more-JavaScripty heterogenous array of numbers and strings. Any practical consumer of this format will likely traverse an object tree using the index operator, which should work more easily with this format. It also allows easy prefix comparison for consumers which are tracking paths. While updating the documentation to include this new field, I noticed that some others were missing, so added them too.	5 years ago
Rachel Sharp	c302fa507f	Add link to lifecycle tutorial	5 years ago
Martin Atkins	1d3e34e35e	command: New -replace=... planning option This allows a similar effect to pre-tainting an object but does the action within the context of a normal plan and apply, avoiding the need for an intermediate state where the old object still exists but is marked as tainted. The core functionality for this was already present, so this commit is just the UI-level changes to make that option available for use and to explain how it contributed to the resulting plan in Terraform's output.	5 years ago
Martin Atkins	6bed3008a5	website: Reworking of the "terraform plan" docs, and related pages It's been a long time since we gave this page an overhaul, and with our ongoing efforts to make plan and apply incorporate all of the side-effects that might need to be done against a configuration it seems like a good time for some restructuring in that vein. The starting idea here is to formally split the many "terraform plan" options into a few different categories: - Planning modes - Planning options - Other options The planning modes and options are the subset that are also accepted by "terraform apply" when it's running in its default mode of generating a plan and then prompting for interactive approval of it. This then allows us to avoid duplicating all of that information on the "terraform apply" page, and thus allows us to spend more words discussing each of them. This set of docs is intended as a fresh start into which we'll be able to more surgically add in the information about -refresh-only and -replace=... once we have those implemented. Consequently there are some parts of this which may seem a little overwraught for what it's currently describing; that's a result of my having prepared this by just deleting the -refresh-only and -replace=... content from our initial docs draft and submitted the result, in anticipation of re-adding the parts I've deleted here in the very near future in other commits.	5 years ago
Sam Velie	5d04c4ea27	docs: correct spelling of normally (#28508 )	5 years ago
Martin Atkins	b802237e03	plans: Track an optional extra "reason" for some planned actions Previously we were repeating some logic in the UI layer in order to recover relevant additional context about a change to report to a user. In order to help keep things consistent, and to have a clearer path for adding more such things in the future, here we capture this user-facing idea of an "action reason" within the plan model, and then use that directly in order to decide how to describe the change to the user. For the moment the "tainted" situation is the only one that gets a special message, matching what we had before, but we can expand on this in future in order to give better feedback about the other replace situations too. This also preemptively includes the "replacing by request" reason, which is currently not reachable but will be used in the near future as part of implementing the -replace=... plan command line option to allow forcing a particular object to be replaced. So far we don't have any special reasons for anything other than replacing, which makes sense because replacing is the only one that is in a sense a special case of another action (Update), but this could expand to other kinds of reasons in the future, such as explaining which of the few different reasons a data source read might be deferred until the apply step.	5 years ago
Kristin Laemmert	f6af7b4f7a	lang/funcs: add (console-only) TypeFunction (#28501 ) * lang/funcs: add (console-only) TypeFunction The type() function, which is only available for terraform console, prints out the type of a given value. This is mainly intended for debugging - it's nice to be able to print out terraform's understanding of a complex variable. This introduces a new field for Scope: ConsoleMode. When ConsoleMode is true, any additional functions intended for use in the console (only) may be added.	5 years ago
Rachel Sharp	98ce186be9	Merge pull request #28443 from hashicorp/res-add-learn-link-debug-1 Add Learn link to Debugging	5 years ago
John Houston	fabdf0bea1	Add config_paths and drop KUBECONFIG env variable in kubernetes backend (#26997 )	5 years ago
Rachel Sharp	56483d10d2	Update debugging.html.md	5 years ago
Kristin Laemmert	85adad0ec7	docs: small update for provider binary locations (#28413 ) * docs: add note that provider binaries need to be placed in appropriate subdirectories under the default locations	5 years ago
Martin Atkins	5f5432e8ea	website: v0.15 upgrade guide for sensitive resource attributes (#28355 ) * website: v0.15 upgrade guide for sensitive resource attributes Our earlier draft of this guide didn't include a section about the stabilization of the "provider_sensitive_attrs" language experiment. This new section aims to address the situation where a module might previously have been returning a sensitive value without having marked it as such, and thus that module will begin returning an error after upgrading to Terraform v0.15. As part of that, I also reviewed the existing documentation about these features and made some edits aiming to make these four different sections work well together if users refer to them all at once, as they are likely to do if they follow the new links from the upgrade guide. I aimed to retain all of the content we had before, but some of it is now in a new location. In particular, I moved the discussion about the v0.14 language experiment into the upgrade guide, because it seems like a topic only really relevant to those upgrading from an earlier version and not something folks need to know about if they are using Terraform for the first time in v0.15 or later. * minor fixups Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
Martin Atkins	140c613ae8	lang/funcs: "one" function In the Terraform language we typically use lists of zero or one values in some sense interchangably with single values that might be null, because various Terraform language constructs are designed to work with collections rather than with nullable values. In Terraform v0.12 we made the splat operator [*] have a "special power" of concisely converting from a possibly-null single value into a zero-or-one list as a way to make that common operation more concise. In a sense this "one" function is the opposite operation to that special power: it goes from a zero-or-one collection (list, set, or tuple) to a possibly-null single value. This is a concise alternative to the following clunky conditional expression, with the additional benefit that the following expression is also not viable for set values, and it also properly handles the case where there's unexpectedly more than one value: length(var.foo) != 0 ? var.foo[0] : null Instead, we can write: one(var.foo) As with the splat operator, this is a tricky tradeoff because it could be argued that it's not something that'd be immediately intuitive to someone unfamiliar with Terraform. However, I think that's justified given how often zero-or-one collections arise in typical Terraform configurations. Unlike the splat operator, it should at least be easier to search for its name and find its documentation the first time you see it in a configuration. My expectation that this will become a common pattern is also my justification for giving it a short, concise name. Arguably it could be better named something like "oneornull", but that's a pretty clunky name and I'm not convinced it really adds any clarity for someone who isn't already familiar with it.	5 years ago
Víctor Felipe Godoy Hernández	a9487c7674	Fix yamldecode example from json to yaml (#28220 ) * Fix yamldecode example from json to yaml * inline yaml example	5 years ago
Martin Atkins	f47c4efb1b	website: Dynamic blocks can for_each any collection type We previously added a hint to both resource for_each and dynamic blocks about using the "flatten" and "setproduct" situations to construct suitable collections to repeat over. However, we used the same text in both places which ended up stating that dynamic blocks can only accept map or set values, which is a constraint that applies to resource for_each (because we need to assign a unique identifier to each instance) and not to dynamic blocks (which don't have any uniqueness enforced by Terraform Core itself). To remove that contradiction with the text above which talks about what is valid here, I've just generalized this to say "collection", because the primary point of this paragraph is the "one element per desired nested block" part, not specifically what sort of collections are permitted in this location. (Text further up describes the supported types.)	5 years ago
Robin Norwood	e3bd661470	Merge pull request #28164 from hashicorp/rln-add-resource-targeting-tutorial-callout Add callout to resource targeting tutorial	5 years ago
Matthew Frahry	15779013da	backend/azurerm: Bug fixes and updated dependencies #28181	5 years ago
Judith Malnick	75fbbe8065	clarify version that pull upgrades local state to (#28204 )	5 years ago
Martin Atkins	6f35c2847b	command: Reorganize docs of the local backend's legacy CLI options We have these funny extra options that date back to before Terraform even had remote state, which we've preserved along the way by most recently incorporating them as special-case overrides for the local backend. The documentation we had for these has grown less accurate over time as the details have shifted, and was in many cases missing the requisite caveats that they are only for the local backend and that backend configuration is the modern, preferred way to deal with the use-cases they were intended for. We always have a bit of a tension with this sort of legacy option because we want to keep them documented just enough to be useful to someone who finds an existing script/etc using them and wants to know what they do, but not to take up so much space that they might distract users from finding the modern alternative they should consider instead. As a compromise in that vein here I've created a new section about these options under the local backend documentation, which then gives us the space to go into some detail about the various behaviors and interactions and also to discuss their history and our recommended alternatives. I then simplified all of the other mentions of these in command documentation to just link to or refer to the local backend documentation. My hope then is that folks who need to know what these do can still find the docs, but that information can be kept out of the direct path of new users so they can focus on learning about remote backends instead. This is certainly not the most ideal thing ever, but it seemed like the best compromise between the competing priorities I described above.	5 years ago
Matthew Frahry	13b41d59f5	Website Test Fix	5 years ago
Matthew Frahry	3546650ac6	backend/azurerm: adding the right role name	5 years ago
Robin Norwood	31323b911b	Add callout to resource targeting tutorial	5 years ago
Matthew Frahry	a978d4ee99	website: adding the new fields to azurerm	5 years ago
Tej-Singh-Rana	2a49d908b8	fix the typo (#28140 )	5 years ago
Pam Selle	683422e54f	Merge pull request #28113 from hashicorp/pselle/provider_sensitive_attrs_docs Update documentation for provider_sensitive_attrs experiment	5 years ago
James Bardin	c6278bbe37	Merge pull request #28042 from jasons42/update-workspaces-docs Indicate etcdv3 support for multiple workspaces in docs	5 years ago
Alisdair McDiarmid	b6ca782993	documentation: Clarify JSON diagnostic traversal The traversal value is normally a valid HCL string, but can be simplified if a traversal step has a complex index value (e.g. an object). This means it is not always parseable HCL, so this commit updates the documentation to clarify this and explicitly record that we do not guarantee its contents are stable. The purpose of these values is purely for building human-readable UI.	5 years ago
Alisdair McDiarmid	53739f0aac	Merge pull request #28108 from hashicorp/alisdair/validate-json-format-version cli: Add format version to validate -json output	5 years ago
Martin Atkins	89b2405080	lang/funcs: "sensitive" and "nonsensitive" functions These aim to allow hinting to Terraform about situations where it's not able to automatically infer value sensitivity. "nonsensitive" is for situations where Terraform's behavior is too conservative, such as when a new value is derived from a sensitive value in such a way that all of the sensitive content is removed. "sensitive", on the other hand, is for situations where Terraform can't otherwise infer that a value is sensitive. These situations should be pretty rare in a module that's making effective use of sensitive input variables and output values, but the documentation shows one example of an uncommon situation where a more direct hint via this function would be needed. Both of these functions are aimed at only occasional use in unusual situations. They are here for reasons of pragmatism, not because we expect them to be used routinely or recommend their use.	5 years ago
Paddy	0b5c4a6a2c	Accept TF_LOG=json to enable TRACE logs in JSON format This is not currently a supported interface, but we plan to release tool(s) that consume parts of it that are more dependable later, separately from Terraform CLI itself.	5 years ago
Pam Selle	81e8167a4c	Update documentation for provider_sensitive_attrs experiment Update documentation to reference that this experiment is now default in 0.15+	5 years ago
Alisdair McDiarmid	46a29b13ed	cli: Add format version to validate -json output In line with the other complex JSON output formats for plan and provider schema, here we add an explicit `format_version` field to the JSON output of terraform validate.	5 years ago
Alisdair McDiarmid	2a85f0483f	website: Update validate -json diags documentation Updated to include details about the new "snippet" object in JSON diagnostics.	5 years ago
Martin Atkins	dc7f2b7314	website: docs for the terraform validate JSON output	5 years ago
Jason Smith	024035114a	Fix broken link error Link to https://consul.io/ is not actually broken but returns a 307 redirect to https://www.consul.io/ which the broken link test counts as a failure.	5 years ago
Jason Smith	8663b2100a	Indicate etcdv3 support for multiple workspaces	5 years ago
Antoine Cotten	3442873cdb	docs: Update link to HCL native syntax spec	5 years ago
Masayuki Morita	31a5aa1878	command/init: Add a new flag `-lockfile=readonly` (#27630 ) Fixes #27506 Add a new flag `-lockfile=readonly` to `terraform init`. It would be useful to allow us to suppress dependency lockfile changes explicitly. The type of the `-lockfile` flag is string rather than bool, leaving room for future extensions to other behavior variants. The readonly mode suppresses lockfile changes, but should verify checksums against the information already recorded. It should conflict with the `-upgrade` flag. Note: In the original use-case described in #27506, I would like to suppress adding zh hashes, but a test code here suppresses adding h1 hashes because it's easy for testing. Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	5 years ago
Aaron Lane	f172585eaa	Fix Kitchen-Terraform language in test experiment This isn't incredibly important, but Kitchen-Terraform is written in and requires tests to be written in Ruby.	5 years ago
Kristin Laemmert	106bcd3bf0	update to match new default branch name (#27909 )	5 years ago
Alisdair McDiarmid	79f855b83b	Merge pull request #27840 from OJFord/docs-27554 Document `inline` & `on_failure` behaviour	5 years ago
Rachel Sharp	3cb4918739	Merge pull request #27862 from hashicorp/add-state-learn-tutorial Add State Learn tutorial to State docs	5 years ago
James Bardin	c103242bef	Merge pull request #27885 from hashicorp/jbardin/show-json jsonstate: indicate schema version mismatch during encoding	5 years ago
James Bardin	c7995b7d4b	update show -json docs	5 years ago
Martin Atkins	8d37a70987	website: Initial docs for the module integration testing experiment Since this is still at an early phase and likely to change significantly in future iterations, rather than attempting to guess on a suitable final location for documenting the testing feature I've instead taken the unusual approach of adding a new page that is explicitly about the experiment. My expectation is that once we conclude the experiment we'll replace this new page with a stub that just explains that there was once an experiment and then links to whatever final feature unfolded from the research. The URL for this page is hard-coded into the warning message in the "terraform test" command, so as we continue to evolve this feature in future releases we'll need to update the callout note on the page about which Terraform CLI version it's currently talking about, so users of older versions can clearly see when they'd need to upgrade in order to participate in a later incarnation of the experiment.	5 years ago
Rachel Sharp	2f287b41de	Add State Learn tutorial to State docs	5 years ago
Oliver Ford	2f7c368d91	Document `inline` & `on_failure` behaviour cf. #27554	5 years ago
Pam Selle	8d2fbd4cd8	Remove deprecation on undeclared variable, docs, and summary adjustment (#27795 ) * Remove deprecation on undeclared variable Remove deprecation and add docs specific to the behavior around undeclared variable values * Limit full warnings to 2 instances, then summary This way, the third warning is a summary, rather than the fourth warning being the summary	5 years ago
James Bardin	d54a9b176b	Update website/docs/language/providers/configuration.html.md Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
James Bardin	e40727076f	Update website/docs/language/modules/develop/providers.html.md Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
James Bardin	9859d4e70b	Update website/docs/language/modules/develop/providers.html.md Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
James Bardin	dfd8424392	link configuration aliases between pages	5 years ago
James Bardin	1bb602859a	update docs for configuration_aliases Remove references to the "proxy configuration block" concept, and add examples showing the usage of `configuration_aliases`.	5 years ago
Stephen	e39abbf6f0	fix regex logical or documentation (#27637 ) * fix regex logical or documentation Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
Robin Norwood	181048b913	Add crosslink to new Learn tutorial	5 years ago
Alisdair McDiarmid	888f36aebb	cli: Remove positional plan argument from graph To make the command arguments easier to understand and extend, we are moving away from positional arguments. This commit changes the graph command to take a `-plan` flag instead of an optional trailing path.	5 years ago
Pam Selle	6da55c0521	Update grammar for flags	5 years ago
Andor Markus	f658531883	Updating terraform workspace website list.html.md new.html.md select.html.md files thus it reflect the current version of Terraform CLI	5 years ago
Pam Selle	e1b0e3ce92	Remove -module option for taint and untaint This has been an error with help text, and can be removed.	5 years ago
Alisdair McDiarmid	75d38b50b1	docs: Note: state pull upgrades to current version	5 years ago
Nick Fagerlund	6d016af7c5	website: Remove links to legacy provider docs for GitHub, ksyun These providers are now published to the registry, as planned.	5 years ago
Nick Fagerlund	4e4f6b3f42	website: Restore note about standard vs. enhanced backends	5 years ago
Nick Fagerlund	33d2d9abb5	website: CLI: Remove several ghost pages, update old links - /docs/plugins/* - /docs/commands/state/addressing.html These were redundant pages.	5 years ago
Nick Fagerlund	d1e8537b33	website: CLI: Update links to moved docs pages	5 years ago
Nick Fagerlund	a8332703c9	website: CLI: Move docs files to match new URLs	5 years ago
Nick Fagerlund	b909a4a3a1	website: Move hidden attr-as-blocks page into new URL structure This is a "ghost page" that remains relevant and useful, under certain rare circumstances.	5 years ago
Nick Fagerlund	8cfcd82be3	website: Language: Remove several ghost pages, update links During the language/CLI docs reorg, we noticed several pages that were no longer viable; some were redundant, some useless, and some just very obsolete. Since we were trying to avoid breaking links at the time, we opted to remove them from the navs and leave them as "ghost pages" — still accessible, but not findable. This commit finally cleans these ghosts up and updates any remaining links to relevant modern pages. Bustin' makes me feel good. 👻🚫	5 years ago
Nick Fagerlund	7a8dd326c6	website: Language: Update links to moved pages	5 years ago
Nick Fagerlund	78dcc8dc1b	website: Language: Move files to match new URL structure	5 years ago
Nick Fagerlund	22d7c11d8a	website: Language: Remove the "this is 0.12+" message from language docs The sun has set on 0.11, so the value of maintaining this message on nearly every page has crashed to almost zero. Time to pull it.	5 years ago
fredtrimble	7b3b401da4	Update index.html.md Change the word "date" to "data"	5 years ago
Pam Selle	61f9d2177b	Merge pull request #27486 from hashicorp/pselle/version-doc Add documentation page for version	5 years ago
Rémy Léone	edb4c00a86	website: add links to the registry provider documentation (#27416 ) * docs: add links to the registry provider documentation * Adjust wording/link URL Co-authored-by: Nick Fagerlund <nick@hashicorp.com>	5 years ago
Nick Fagerlund	303b326008	Merge pull request #27279 from kowshikRoy/add-var-multiple-example website: add example of multiple var cli	5 years ago
Nick Fagerlund	66f2c82d33	website: Add version command to sidebar nav and to plugins overview page	5 years ago
Pam Selle	cf0c54f834	Add documentation page for version The version command, although not the mightiest of our commands, did not have a page among our docs.	5 years ago
Pam Selle	ae52190c01	Merge pull request #27415 from techsolx/patch-1 Chage backend.tmpl to config.tmpl in Maps example,	5 years ago
Pam Selle	516ad2c8e4	Merge pull request #27432 from bulletinmybeard/patch-1 Update gcs.html.md	5 years ago
Pam Selle	e22ccd424c	Add note about removal to web docs	5 years ago
Cladius Fernando	25003a0caa	Corrected minor typo On Windows, the file must be named named terraform.rc => On Windows, the file must be named terraform.rc	5 years ago
Robin Schulz	64f9180a3c	Update gcs.html.md Just a typo	5 years ago
Chris Arcand	5440d9653b	[skip-ci] Remove documentation on 'CONFIRM_DESTROY' This variable mechanism was replaced long ago with a explicit `Allow destroy plans` setting on a Terraform Cloud workspace, and no longer does anything: https://www.terraform.io/docs/cloud/workspaces/settings.html#destruction-and-deletion Rather than mention this new mechanism at all though, I've removed the requisite from here entirely - the reason being that a consideration like this is no different from other permission concerns (e.g. "You must have Apply permission on a workspace to `apply`"), and without enumerating _all_ of these here - which doesn't seem appropriate - we just remove this concern entirely.	5 years ago
JohnM	72e657edcc	Chage backend.tmpl to config.tmpl in Maps example, Reference file in Maps example is named config.tmpl, example used backend.tmpl from previous section.	5 years ago
Nick Fagerlund	5ceb8b2b98	website: Adopt `terraform_remote_state` into language docs ...and also shrink the explanation for alternate sharing approaches, a bit. Actually, it looks like I already half-adopted it by accident. 😬 But this commit adds it to the sidebar under "State", so users can browse to it. I'm leaving the URL alone, because it's not urgent and we'll need to adjust a large swath of URLs at some point anyway. This change effectively stops presenting `terraform` as a provider in the normal sense, and reduces /docs/providers/terraform/index.html to a ghost page in the language section (to avoid breaking links for the time being). The message a reader should get is that Terraform has one special built-in data source where you don't need to think about the provider or its version.	5 years ago
stakiran	3ce7edc018	website: Fix wrong link of operators. not "references.html" but "operators.html".	5 years ago
Nick Fagerlund	cc6a226bcf	website: Remove provider category indexes, reduce main list As of December 18, 2020, we've redirected nearly all of the provider documentation that used to live on terraform.io: - For providers that got published on the Registry, we redirected each docs page to the corresponding Registry docs page. - For providers that never got adopted by a new publisher, we archived the GitHub repository and redirected each docs page to the corresponding Markdown source file on github.com. (For an example of these redirects, see https://www.terraform.io/docs/providers/telefonicaopencloud/r/s3_bucket.html) There are ten providers left that we haven't redirected. These ones got adopted by new publishers and _will_ end up on the Registry, but they aren't quite ready to ship and get their permanent redirects, and we don't want to sabotage their SEO by 301ing to a temporary destination.	5 years ago
Robin Norwood	235c141565	Add links to outputs and locals tutorials	5 years ago
Nick Fagerlund	85d477aee9	website: Fix numerous links with redirects or broken anchors These links largely still go somewhere useful, but they have some kind of issue revealed by our new link checker: - Some of them point to a stale URL that redirects, and can be updated to the new destination. - Some of them point to anchors that don't exist (anymore?) in the destination. - Some of them end up redirecting unnecessarily due to how the server handles directory URLs without trailing slashes. Sorry, I know that's pointless, just, humor me for the time being so we can get our CI green. 😭 In a couple cases, I've added invisible anchors to destination pages, either to preserve an old habit or because the current anchors kind of suck due to being particularly long or meandering.	5 years ago
Nick Fagerlund	1fff4e2690	website: Update links to redirected provider docs pages This commit intentionally leaves the indexes of provider docs alone, to avoid merge conflicts when we delete those.	5 years ago
Pam Selle	1970c14a53	[docs] Add limitations section to for_each (#27299 ) * Add limitations section to for_each Move limitations from a note to their own section, to allow for expansion on disallowing sensitive values in for_each	5 years ago
Pam Selle	d7f3239c51	Document sensitivity + function call behavior	5 years ago
Repon Kumar Roy	7d093cbede	website: add example of multiple var cli This PR updates the documentation of input variable of terraform. It's mentioned that multiple `-var` is possible, but no example is given. This PR adds an example of multiple `-var` option	5 years ago
Kristin Laemmert	8bab3dd374	command/state list: list resources in nested and expanded modules (#27268 ) * command/state list: list resources in nested and expaneded modules A few distinct bugs fixed in here: There was a bug in the logic checking if a given module was the child of the targetAddr, now fixed. That resolved the basic issue where resources in nested submodules were not listed. The logic around allowMissing needed some tweaking to allow for empty modules, as long as those modules had submodules with resources. state list is the only command using allowMissing with false so this felt safe to do. Finally I extended the logic so list would included expanded modules, which is to say giving module.foo would result in resources from module.foo[1], module.foo[0], etc. * update state list docs to show that module filtering includes any nested modules	5 years ago
James Bardin	cd4cb3f8d2	add implied data depends_on caveat	5 years ago
Martin Atkins	3268a7eaba	command/output: Raw output mode So far the output command has had a default output format intended for human consumption and a JSON output format intended for machine consumption. However, until Terraform v0.14 the default output format for primitive types happened to be _almost_ a raw string representation of the value, and so users started using that as a more convenient way to access primitive-typed output values from shell scripts, avoiding the need to also use a tool like "jq" to decode the JSON. Recognizing that primitive-typed output values are common and that processing them with shell scripts is common, this commit introduces a new -raw mode which is explicitly intended for that use-case, guaranteeing that the result will always be the direct result of a string conversion of the output value, or an error if no such conversion is possible. Our policy elsewhere in Terraform is that we always use JSON for machine-readable output. We adopted that policy because our other machine-readable output has typically been complex data structures rather than single primitive values. A special mode seems justified for output values because it is common for root module output values to be just strings, and so it's pragmatic to offer access to the raw value directly rather than requiring a round-trip through JSON.	5 years ago
Pam Selle	aa044bdd39	Fix docs for 0.15 for vendor provisioners	5 years ago
Hyunsuk Shin	16f8baa40e	Update setproduct.html.md (#27184 ) fill wrong syntax	5 years ago
Martin Atkins	776b33db32	website: Recommend against making JSON/YAML with heredocs This is a repeated cause of confusion and questions in the community forum, because both JSON and YAML valid syntax are hard to generate using just string concatenation. Terraform has built-in functions for both of these common serializations to avoid those problems, and so this will hopefully make these better alternatives more discoverable.	5 years ago
Martin Atkins	ab1dd87540	website: Elaborate the "expressions" sub-pages in the language section When we did the earlier documentation rework for Terraform v0.12 we still had one big "Expressions" page talking about the various operators and constructs, and so we had to be a bit economical with the details about some more complicated constructs in order to avoid the page becoming even more overwhelming. However, we've recently reorganized the language documentation again so that the expressions section is split across several separate pages, and that gives some freedom to go into some more detail about and show longer examples for certain features. My changes here are not intended to be an exhaustive rewrite but I did try to focus on some areas I've commonly seen questions about when helping in the community forum and elsewhere, and also to create a little more connectivity between the different content so readers can hopefully find what they are looking for more easily when they're not yet sure what terminology to look for.	5 years ago

1 2 3 4 5 ...

1454 Commits (dc0dd75b602fef76d55a67f0aab0eb7016b995ce)