terraform

Commit Graph

Author	SHA1	Message	Date
Laura Pacilio	06a2fdcf9d	Merge branch 'main' into description-metadata-language-docs	5 years ago
Laura Pacilio	a780f625e9	Fix metadata description format on all pages	5 years ago
Kristin Laemmert	563f1436eb	various docs updates (#29018 ) * website/docs: add sensitivity warning to output documentation fixes #28005 * website/docs: add note about ** to fileset documentation closes #24220 * website/docs: add note that `dynamic` expressions aren't included in json config output closes #28346 * website: the provider installer isn't necessarily concurrency safe closes #28367	5 years ago
Laura Pacilio	bc9065334e	Update description metadata per PR feedback	5 years ago
Laura Pacilio	952cb33103	Add description metadata to functions overview page	5 years ago
Laura Pacilio	577c3653f2	Merge pull request #28983 from KurtLehnardt/patch-1 fixed typo	5 years ago
Laura Pacilio	de97a03528	Merge pull request #28908 from kondr57/patch-1 fix typo	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	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
James Bardin	760a59b3a7	negative substring	5 years ago
Steve Matney	e27a927ba4	Updating sensitive and nonsensitive docs with correct v0.15 info.	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	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
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
Nick Fagerlund	d1e8537b33	website: CLI: Update links to moved docs pages	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

20 Commits (277fe647b95e32b9ca0738cd20af09735954dfd8)