90 Commits (6440c839474f052d8997bb5cec19c2743e5108e6)

Author	SHA1	Message	Date
Pam Selle	2a35240a17	Merge pull request #26314 from hashicorp/remove-template-provider-link ... docs: remove link to deprecated provider	5 years ago
Alejandro Rosero Vicuña	6d66b8b616	website: Make template file extension more consistent (#25029) ... Co-authored-by: Judith Malnick <judith.patudith@gmail.com>	6 years ago
Arthur Burkart	6ed47c7241	lang/funcs: Add "alltrue" function (#25656) ... This commit adds an `alltrue` function to Terraform configuration. A reason we might want this function is because it will enable more powerful custom variable validations. For example: ```hcl variable "amis" { type = list(object({ id = string })) validation { condition = (alltrue([ for a in var.amis : length(a.id) > 4 && substr(a.id, 0, 4) == "ami-" ])) error_message = "The ID of at least one AMI was invalid." } } ```	6 years ago
kmoe	f12bb4698e	remove link to deprecated provider	6 years ago
Brian Flad	db2b710776	docs/function/timestamp: Mention Time Provider (#26232) ... This utility Terraform Provider has resources designed to handle and store time information by participating normally in the graph.	6 years ago
Jon "The Nice Guy" Spriggs	6f9ce7310c	Website: Add map example to templatefile function docs (#26126) ... This change adds an example of using a map with a few keys and shows how it runs it. Co-authored-by: Nick Fagerlund <nick@hashicorp.com>	6 years ago
Alisdair McDiarmid	9f19034fee	website: Document jsonencode entity escaping	6 years ago
Pam Selle	f2d213c461	Merge pull request #25657 from pdecat/typo_hierarchical ... Typo: heirarchical => hierarchical	6 years ago
Nicolas Vogel	8f42f0fa77	Fix documentation example for the indent function ... We must use interpolation, using the %{} directive will trigger the following error "indent" is not a valid template control keyword	6 years ago
Patrick Decat	062865735f	Typo: heirarchical => hierarchical	6 years ago
Kristin Laemmert	c4ce84269a	website/docs: document difference in formatting strings with width and precision (#25499)	6 years ago
Alisdair McDiarmid	c093c50c80	Merge pull request #25255 from unki/patch-1 ... fix yamldecode()-example, missing a file() call	6 years ago
jessica-ritter	edbf59ed4c	what happens when prefix is not in string ... https://github.com/hashicorp/terraform/blob/master/lang/functions.go#L126 shows that Terraform's Trimprefix comes directly from the standard go library. When prefix is absent in the go standard library, the original string is returned; https://golang.org/pkg/strings/#TrimPrefix.	6 years ago
unki	214009e0f3	fix yamldecode()-example, missing a file() call	6 years ago
Martin Atkins	d1bc412220	configs: Custom variable validation is no longer experimental ... All of the feedback from the experiment described enhancements that can potentially be added later without breaking changes, so this change simply removes the experiment gate from the feature as originally implemented with no changes to its functionality. Further enhancements may follow in later releases, but the goal of this change is just to ship the feature exactly as it was under the experiment. Most of the changes here are cleaning up the experiment opt-ins from our test cases. The most important parts are in configs/experiments.go and in experiments/experiment.go .	6 years ago
Daniel Dreier	44e3d99409	Merge pull request #24659 from hashicorp/timestamp-doc ... specify that `timestamp` returns UTC	6 years ago
Daniel Dreier	5e35dedc2a	Update website/docs/configuration/functions/timestamp.html.md ... Co-authored-by: Matthew Sanabria <24284972+sudomateo@users.noreply.github.com>	6 years ago
Daniel Dreier	7aa97f415d	Fix "additoinal" typo in web site ... Fixes 24769	6 years ago
Noah Mercado	d4d8812afa	Feature: Sum Function (#24666) ... The sum function takes a list or set of numbers and returns the sum of those numbers.	6 years ago
Namho Kim	9cc658b491	specify that `timestamp` returns UTC	6 years ago
Eduard Tamsa	534ba630e4	docs(flatten): Fix typos (#24492)	6 years ago
Adam Leskis	4f85a1a6ba	website: fix simple typo (#24415)	6 years ago
Martin Atkins	67d95b97ce	lang/funcs: templatefile requires valid variable names ... Previously the templatefile function would permit any arbitrary string as a variable name, but due to the HCL template syntax it would be impossible to refer to one that isn't a valid HCL identifier without causing an HCL syntax error. The HCL syntax errors are correct, but don't really point to the root cause of the problem. Instead, we'll pre-verify that the variable names are valid before we even try to render the template, and given a specialized error message that refers to the vars argument expression as the problematic part, which will hopefully make the resolution path clearer for a user encountering this situation. The syntax error still remains for situations where all of the variable names are correct but e.g. the user made a typo referring to one, which makes sense because in that case the problem _is_ inside the template.	6 years ago
James Bardin	4185aa93f5	doc typo	6 years ago
James Bardin	a765d69fb0	Merge pull request #24032 from hashicorp/jbardin/map-funcs ... make the merge function more precise	6 years ago
James Goodhouse	25bfe7337b	lang: add setsubtract function (#23424) ... * add setdifference and setsubtract functions and docs * remove setdifference as it is not implemented correct in underlying lib * Update setintersection.html.md * Update setproduct.html.md * Update setunion.html.md	6 years ago
James Bardin	529271e0be	update merge docs to match behavior	6 years ago
ZMI-RyanMann	66411b5ca0	website/docs: Updated documentation for range function pseudocode (#23823)	6 years ago
Martin Atkins	ff4ea042c2	config: Allow module authors to specify validation rules for variables ... The existing "type" argument allows specifying a type constraint that allows for some basic validation, but often there are more constraints on a variable value than just its type. This new feature (requiring an experiment opt-in for now, while we refine it) allows specifying arbitrary validation rules for any variable which can then cause custom error messages to be returned when a caller provides an inappropriate value. variable "example" { validation { condition = var.example != "nope" error_message = "Example value must not be \"nope\"." } } The core parts of this are designed to do as little new work as possible when no validations are specified, and thus the main new checking codepath here can therefore only run when the experiment is enabled in order to permit having validations.	6 years ago
Martin Atkins	02576988c1	lang: "try" and "can" functions ... These are intended to make it easier to work with arbitrary data structures whose shape might not be known statically, such as the result of jsondecode(...) or yamldecode(...) of data from a separate system. For example, in an object value which has attributes that may or may not be set we can concisely provide a fallback value to use when the attribute isn't set: try(local.example.foo, "fallback-foo") Using a "try to evaluate" model rather than explicit testing fits better with the usual programming model of the Terraform language where values are normally automatically converted to the necessary type where possible: the given expression is subject to all of the same normal type conversions, which avoids inadvertently creating a more restrictive evaluation model as might happen if this were handled using checks like a hypothetical isobject(...) function, etc.	6 years ago
Martin Atkins	bfbd00a23c	website: Note about using jsonencode/yamlencode in templatefile ... It's a common source of errors to try to produce JSON or YAML syntax using string concatenation via our template language but to miss some details like correct string escaping, quoting, required commas, etc. The jsonencode and yamlencode functions are a better way to generate JSON and YAML, but it's not immediately obvious that both of these functions are available for use in external templates (via templatefile) too. Given that questions related to this come up a lot in our community forum and elsewhere, it seems worth having a documentation section to show the pattern of having a template that consists only of a single function call.	6 years ago
Graham Davison	e32641c9ce	website/docs: Corrects function name in `cidrsubnets` function documentation (#23473)	6 years ago
George Christou	91100c003c	lang/funcs: Add more `trim*` functions (#23016) ... * lang/funcs: Add `trim*` functions	6 years ago
Yuki Ito	72c910cebc	website: Fix typographical errors in the docs for base64sha256/512	6 years ago
Martin Atkins	047733d20c	website: Full examples for for_each with flatten and setproduct ... A very common question since we launched the two repetition constructs is how to deal with situations where the input data structure doesn't match one-to-one with the desired configuration. This adds some full worked examples of two common situations that have come up in questions. To avoid adding a lot of extra content to the already-large "expressions" and "resources" pages, the main bulk of this new content lives with the relevant functions themselves as a full example of one thing they are good for, and then we'll link to them from the two general documentation sections where folks are likely to be reading when they encounter the problem.	6 years ago
Martin Atkins	25222fccd5	website: Link to hashicorp/subnets/cidr for cidrsubnets docs ... The cidrsubnets function signature is intentionally very low-level and focused on the core requirement of generating addresses. This registry module then wraps it with some additional functionality to make it more convenient to generate and use subnet address ranges.	7 years ago
Martin Atkins	f84ab99b7d	lang/funcs: cidrsubnets function ... This is a companion to cidrsubnet that allows bulk-allocation of multiple subnet addresses at once, with automatic numbering. Unlike cidrsubnet, cidrsubnets allows each of the allocations to have a different prefix length, and will pack the networks consecutively into the given address space. cidrsubnets can potentially create more complicated addressing schemes than cidrsubnet alone can, because it's able to take into account the full set of requested prefix lengths rather than just one at a time.	7 years ago
Jeet Parekh	bcc69c05bb	lang/funcs: parseint function	7 years ago
Pam Selle	f9ebae749c	Merge pull request #22707 from vsimon/spell ... docs: Minor spelling and typo fixes	7 years ago
Vicken Simonian	853a0e0677	docs: Minor spelling and typo fixes	7 years ago
Brian Flad	19cf34114f	lang/funcs: Switch fileset() function glob implementation to github.com/bmatcuk/doublestar to support additional glob patterns ... This allows the usage of the glob patterns `**` and `{alternative1,...}` to simplify Terraform configuration logic for more complex file matching.	7 years ago
Brian Flad	af7f6ef441	lang/funcs: Update fileset() function to include path as separate first argument, automatically trim the path argument from results, and ensure results are always canonical with forward slash path separators ... Reference: https://github.com/hashicorp/terraform/pull/22523#pullrequestreview-279694703 These changes center around better function usability and consistency with other functions. The function has not yet been released, so these breaking changes can be applied safely.	7 years ago
Pam Selle	6e614f3465	Fix docs mistake/misleading	7 years ago
Brian Flad	d48d9ed766	lang/funcs: Add fileset function ... Reference: https://github.com/hashicorp/terraform/issues/16697 Enumerates a set of regular file names from a given glob pattern. Implemented via the Go stdlib `path/filepath.Glob()` functionality. Notably, stdlib does not support `**` or `{}` extended patterns. See also: https://github.com/golang/go/issues/11862 To support the extended glob patterns, it will require adding a dependency on a third party library or adding our own matching code.	7 years ago
Martin Atkins	135afaeb9c	lang: "regex" and "regexall" functions ... These existing upstream cty functions allow matching strings against regular expression patterns, which can be useful if you need to consume a non-standard string format that Terraform doesn't (and can't) have a built-in function for.	7 years ago
Martin Atkins	5cb80c43c1	website: example of csvdecode with for_each ... We added the csvdecode function originally with the intent of it being used with for_each, but because csvdecode was released first we had a section in its documentation warning about the downsides of using it with "count", since that seemed like something people would be likely to try. With resource "for_each" now merged, we can replace that scary section with a more positive example of using these two features together. We still include a paragraph noting that "count" _could_ be used here, but with a caution against doing so. This is in the hope of helping users understand the difference between these two patterns and why for_each is the superior choice for most situations.	7 years ago
Chris Arcand	275ecf96f2	Merge pull request #22042 from hashicorp/012-replace-regex-docs ... Added regex details to replace() docs	7 years ago
Pam Selle	5cd551f716	Merge pull request #21887 from jmcgeheeiv/patch-1 ... Add "leading zeros" for the sake of SEO	7 years ago
Chris Arcand	22385c3198	Added regex details to replace() docs	7 years ago
Andreas Sommer	042aead714	lang/funcs: add "abspath" function (#21409)	7 years ago