136 Commits (f-workspaces2-prototype)

Author	SHA1	Message	Date
Martin Atkins	3852814797	projects: Find all the workspaces for a project	6 years ago
James Bardin	3839405d3d	correctly evaluate self in for_each resources ... The fallback type for GetResource from an EachMap is a cty.Object, because resource schemas may contain dynamically typed attributes. Check for an Object type in the evaluation of self, to use the proper GetAttr method when extracting the value.	6 years ago
James Bardin	1ee851f256	Merge pull request #22846 from hashicorp/jbardin/evaluate-resource ... Always evaluate resources in their entirety	6 years ago
James Bardin	bfce78064b	lang/eval: more evalContext fixups ... self references do not need to be added to `managedResource`, and in fact that could cause issues later if self is allowed in contexts other than managed resources. Coalesce 2 cases in the Referenceable switch, be take the ContainingResource address of an instance beforehand.	6 years ago
Martin Atkins	39e609d5fd	vendor: switch to HCL 2.0 in the HCL repository ... Previously we were using the experimental HCL 2 repository, but now we'll shift over to the v2 import path within the main HCL repository as part of actually releasing HCL 2.0 as stable. This is a mechanical search/replace to the new import paths. It also switches to the v2.0.0 release of HCL, which includes some new code that Terraform didn't previously have but should not change any behavior that matters for Terraform's purposes. For the moment the experimental HCL2 repository is still an indirect dependency via terraform-config-inspect, so it remains in our go.sum and vendor directories for the moment. Because terraform-config-inspect uses a much smaller subset of the HCL2 functionality, this does still manage to prune the vendor directory a little. A subsequent release of terraform-config-inspect should allow us to completely remove that old repository in a future commit.	6 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
James Bardin	d4031918d1	parse resource refs correctly ... Now that we only evaluate whole resources, we can parse resource refs correct as the resource, rather than an unknown instance.	7 years ago
James Bardin	c49f976308	change lang eval to also only lookup resources ... Continue only evaluating resource at a whole and push the indexing of the resource down into the expression evaluation. The exception here is that `self` must be an instance which must be extracted from the resource. We now also add the entire resource to the context, which was previously only partially populated with the self referenced instance.	7 years ago
James Bardin	86bf674246	change GetResourceInstance to GetResource ... In order to allow lazy evaluation of resource indexes, we can't index resources immediately via GetResourceInstance. Change the evaluation to always return whole Resources via GetResource, and index individual instances during expression evaluation. This will allow us to always check for invalid index errors rather than returning an unknown value and ignoring it during apply.	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	769f626a0e	lang/funcs: Remove homedir.Expand() and refactor path trimming with filepath.Rel() in fileset() function ... Reference: https://github.com/hashicorp/terraform/pull/22621#pullrequestreview-282259385	7 years ago
Brian Flad	820b79d91d	lang/funcs: Clarification update to MakeFileSetFunc comment for filepath.ToSlash usage	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
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
Pam Selle	e38d588cfc	Merge pull request #22314 from hashicorp/pselle/double-dynamic ... Fix panic on double dynamic blocks	7 years ago
Alex Pilon	e2eb70b737	remove satori/go.uuid in favor of google/uuid	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
Pam Selle	234c1c482a	Add a comment	7 years ago
Pam Selle	cd83e6108d	Fixes issue where attribute in nested is not of list type/is invalid and would panic	7 years ago
Kristin Laemmert	2b14a6b332	lang/funcs: lookup() can work with maps of lists, maps and objects (#22269) ... * lang/funcs: lookup() can work with maps of lists, maps and objects lookup() can already handle aribtrary objects of (whatever) and should handle maps of (whatever) similarly.	7 years ago
Pam Selle	360068b3cb	Merge pull request #21922 from pselle/resource_for_each ... Resource for_each	7 years ago
James Bardin	6e222375c7	invlaid use of dynamic with attrs should not panic ... Mistakenly using dynamic on an attribute will lead to a panic when attempting to resolve variable references with a partial body, because the dynamic blocks have yet to be expanded and validated. Check that the block element type is actually an object before generating a schema.	7 years ago
Pam Selle	7d905f6777	Resource for_each	7 years ago
Radek Simko	5c30bafee0	Merge pull request #22119 from hashicorp/b-chunklist-empty-list ... lang/funcs: Pass through empty list in chunklist	7 years ago
Radek Simko	736fda1613	lang/funcs: Pass through empty list in chunklist	7 years ago
Saverio Miroddi	983af7a183	Allow null values in Compact function ... The function would previously panic when one or more null values were among the arguments. The new behavior treats nulls as empty strings, therefore, it removes them.	7 years ago
Andreas Sommer	042aead714	lang/funcs: add "abspath" function (#21409)	7 years ago
Paul Tyng	ebea080aca	Add missing bool case ... Fixes #20572	7 years ago
Pam Selle	1255ad6722	Don't allow nulls in calls to merge	7 years ago
Lars Eric Scheidler	aa07806bfc	lang/funcs: New "uuidv5" function ... This generates name-based uuids, rather than pseudorandom uuids as with the "uuid" function.	7 years ago
Martin Atkins	382e1ca821	lang: yamldecode and yamlencode functions ... These follow the same principle as jsondecode and jsonencode, but use YAML instead of JSON. YAML has a much more complex information model than JSON, so we can only support a subset of it during decoding, but hopefully the subset supported here is a useful one. Because there are many different ways to _generate_ YAML, the yamlencode function is forced to make some decisions, and those decisions are likely to affect compatibility with other real-world YAML parsers. Although the format here is intended to be generic and compatible, we may find that there are problems with it that'll we'll want to adjust for in a future release, so yamlencode is therefore marked as experimental for now until the underlying library is ready to commit to ongoing byte-for-byte compatibility in serialization. The main use-case here is met by yamldecode, which will allow reading in files written in YAML format by humans for use in Terraform modules, in situations where a higher-level input format than direct Terraform language declarations is helpful.	7 years ago
Martin Atkins	f9a73d48db	lang: "range" function ... This is similar to the function of the same name in Python, generating a sequence of numbers as a list that can then be used in other sequence-oriented operations. The primary use-case for it is to turn a count expressed as a number into a list of that length, which can then be iterated over or passed to a collection function to produce that number of something else, as shown in the example at the end of its documentation page.	7 years ago
Kristin Laemmert	c163ba71db	simplify	7 years ago
Kristin Laemmert	30a924e162	lang/funcs: `matchkeys` - unify type for keys and searchset ... Added higher-level test for matchkeys to exercise mixing types in searchset. This had to be in the functions tests so the HCL auto conversion from tuple to list would occur.	7 years ago
Kristin Laemmert	f2a14d7c18	lang/funcs: fix error when `matchkeys` encountered a variable ... `matchkeys` was returning a (false) error if the searchset was a variable, since then the type of the keylist and searchset parameters would not match. This does slightly change the behavior: previously matchkeys would produce an error if the parameters were not of the same type, for e.g. if searchset was a list of strings and keylist was a list of integers. This no longer produces an error.	7 years ago
James Bardin	0133dda311	allow empty dynamic blocks with ConfigModeAttr ... If a dynamic block is evaluated zero times, the body content will contain 0 blocks. Allow the probe for ConfigModeAttr to accept that no blocks with a matching attribute should still be converted to a block if they are called with dynamicExpand.	7 years ago
Martin Atkins	55794eb658	lang/funcs: Don't panic when distinct called with empty list	7 years ago
Martin Atkins	742deca3e9	lang/funcs: Short-circuit if start or end index is unknown ... Previously the type-selection codepath for an input tuple referred unconditionally to the start and end index values. In the Type callback, only the types of the arguments are guaranteed to be known, so any access to the values must be guarded with an .IsKnown check, or else the function will not short-circuit properly when an unknown value is passed. Now we will check the start and end indices are in range when we have enough information to do so, but we'll return an approximate result if either is unknown.	7 years ago
Kristin Laemmert	b1d0b1383f	lang/funcs: remove sethaselement function and documentation (#21164) ... `contains` and `sethaselement` are effectively the same function, and `contains` works with `sets` thanks to automatic HCL conversion.	7 years ago
James Bardin	3ab496d4b1	allow sets and tuples in contains function ... Sets are no longer going to be automatically converted, so we need to handle those in contains.	7 years ago
James Bardin	19bddee11b	more precise types handling in coalescelist ... coalescelist should accept lists and tuples, and return a dynamic types when the arguments are not homogeneous.	7 years ago
James Bardin	d186d3a490	update slice test	7 years ago
James Bardin	359f057a16	allow chunklist to handle unknowns ... Chunklist should be able to return chunks containing unknown values.	7 years ago
James Bardin	93ef015336	more precise type handling in flatten ... FlattenFunc can return lists and tuples when individual elements are unknown. Only return an unknown tuple if the number of elements cannot be determined because it contains an unknown series. Make sure flatten can handle non-series elements, which were previously lost due to passing a slice value as the argument.	7 years ago
James Bardin	81e04c3050	more precise type handling in slice ... When slicing a list containing unknown values, the list itself is known, and slice should return the proper slice of that list. Make SliceFunc return the correct type for slices of tuples, and disallow slicing sets.	7 years ago
Kristin Laemmert	8520f4e4a5	* lang/funcs/flatten: accept sets and tuples, return tuples ... * lang/funcs: flatten should handle sets and tuples * flatten now returns a tuple	7 years ago
Martin Atkins	6adcc7ab73	vendor: go get github.com/zclconf/go-cty@master ... cty now guarantees that sets of primitive values will iterate in a reasonable order. Previously it was the caller's responsibility to deal with that, but we invariably neglected to do so, causing inconsistent ordering. Since cty prioritizes consistent behavior over performance, it now imposes its own sort on set elements as part of iterating over them so that calling applications don't have to worry so much about it. This change also causes cty to consistently push unknown and null values in sets to the end of iteration, where before that was undefined. This means that our diff output will now consistently list additions before removals when showing sets, rather than the ordering being undefined as before. The ordering of known, non-null, non-primitive values is still not contractually fixed but remains consistent for a particular version of cty.	7 years ago