475 Commits (890eebabc42fb4fdbb0ae90f3a4c1912de71c461)

Author	SHA1	Message	Date
David Glasser	594ea105d8	config: support lists and maps in jsonencode ... For now we only support lists and maps whose values are strings, not deeply nested data.	10 years ago
Martin Atkins	60c24e3319	command: Prevent data resources from being tainted ... Since the data resource lifecycle contains no steps to deal with tainted instances, we must make sure that they never get created. Doing this out in the command layer is not the best, but this is currently the only layer that has enough information to make this decision and so this simple solution was preferred over a more disruptive refactoring, under the assumption that this taint functionality eventually gets reworked in terms of StateFilter anyway.	10 years ago
Martin Atkins	718cdda77b	config: Parsing of data.TYPE.NAME.FIELD variables ... This allows ${data.TYPE.NAME.FIELD} interpolation syntax at the configuration level, though since there is no special handling of them in the core package this currently just acts as an alias for ${TYPE.NAME.FIELD}.	10 years ago
Martin Atkins	860140074f	config: Data source loading ... This allows the config loader to read "data" blocks from the config and turn them into DataSource objects. This just reads the data from the config file. It doesn't validate the data nor do anything useful with it.	10 years ago
Martin Atkins	fc4fa10981	config: "ResourceMode" concept for resources ... Previously resources were assumed to always support the full set of create, read, update and delete operations, and Terraform's resource management lifecycle. Data sources introduce a new kind of resource that only supports the "read" operation. To support this, a new "Mode" field is added to the Resource concept within the config layer, which can be set to ManagedResourceMode (to indicate the only mode previously possible) or DataResourceMode (to indicate that only "read" is supported). To support both managed and data resources in the tests, the stringification of resources in config_string.go is adjusted slightly to use the Id() method rather than the unusual type[name] serialization from before, causing a simple mechanical adjustment to the loader tests' expected result strings.	10 years ago
Mitchell Hashimoto	27452f0043	terraform: Module option to Import to add module to graph	10 years ago
Mitchell Hashimoto	3c9a92e04a	command: Context buliding allows empty module trees	10 years ago
James Nugent	f1d0fc46aa	core: Fix go vet issues shown by Travis	10 years ago
James Nugent	244da895cd	core: Remove StringList ... Much celebration may now ensue! ♪┏(°.°)┛┗(°.°)┓┗(°.°)┛┏(°.°)┓ ♪	10 years ago
James Nugent	f49583d25a	core: support native list variables in config ... This commit adds support for native list variables and outputs, building up on the previous change to state. Interpolation functions now return native lists in preference to StringList. List variables are defined like this: variable "test" { # This can also be inferred type = "list" default = ["Hello", "World"] } output "test_out" { value = "${var.a_list}" } This results in the following state: ``` ... "outputs": { "test_out": [ "hello", "world" ] }, ... ``` And the result of terraform output is as follows: ``` $ terraform output test_out = [ hello world ] ``` Using the output name, an xargs-friendly representation is output: ``` $ terraform output test_out hello world ``` The output command also supports indexing into the list (with appropriate range checking and no wrapping): ``` $ terraform output test_out 1 world ``` Along with maps, list outputs from one module may be passed as variables into another, removing the need for the `join(",", var.list_as_string)` and `split(",", var.list_as_string)` which was previously necessary in Terraform configuration. This commit also updates the tests and implementations of built-in interpolation functions to take and return native lists where appropriate. A backwards compatibility note: previously the concat interpolation function was capable of concatenating either strings or lists. The strings use case was deprectated a long time ago but still remained. Because we cannot return `ast.TypeAny` from an interpolation function, this use case is no longer supported for strings - `concat` is only capable of concatenating lists. This should not be a huge issue - the type checker picks up incorrect parameters, and the native HIL string concatenation - or the `join` function - can be used to replicate the missing behaviour.	10 years ago
James Nugent	e57a399d71	core: Use native HIL maps instead of flatmaps ... This changes the representation of maps in the interpolator from the dotted flatmap form of a string variable named "var.variablename.key" per map element to use native HIL maps instead. This involves porting some of the interpolation functions in order to keep the tests green, and adding support for map outputs. There is one backwards incompatibility: as a result of an implementation detail of maps, one could access an indexed map variable using the syntax "${var.variablename.key}". This is no longer possible - instead HIL native syntax - "${var.variablename["key"]}" must be used. This was previously documented, (though not heavily used) so it must be noted as a backward compatibility issue for Terraform 0.7.	10 years ago
James Nugent	b62f6af158	core: Add support for marking outputs as sensitive (#6559) ... * core: Add support for marking outputs as sensitive This commit allows an output to be marked "sensitive", in which case the value is redacted in the post-refresh and post-apply list of outputs. For example, the configuration: ``` variable "input" { default = "Hello world" } output "notsensitive" { value = "${var.input}" } output "sensitive" { sensitive = true value = "${var.input}" } ``` Would result in the output: ``` terraform apply Apply complete! Resources: 0 added, 0 changed, 0 destroyed. Outputs: notsensitive = Hello world sensitive = <sensitive> ``` The `terraform output` command continues to display the value as before. Limitations: Note that sensitivity is not tracked internally, so if the output is interpolated in another module into a resource, the value will be displayed. The value is still present in the state.	10 years ago
James Nugent	a0cc7115b3	deps: Update call sites of hil.Eval from update ... hil.Eval() now returns (hil.EvaluationResult, error) instead of (value, type, error). This commit updates the call sites, but retains all previous behaviour. Tests are also updated.	10 years ago
James Nugent	d7d39702c0	Type check variables between modules (#6185) ... These tests demonstrates a problem where the types to a module input are not checked. For example, if a module - inner - defines a variable "should_be_a_map" as a map, or with a default variable of map, we do not fail if the user sets the variable value in the outer module to a string value. This is also a problem in nested modules. The implementation changes add a type checking step into the graph evaluation process to ensure invalid types are not passed.	10 years ago
David Glasser	6cf06bb3ab	config: new interpolation function jsonencode	10 years ago
Paul Hinze	293c6ca68c	Revert "Revert "core: Add uuid() interpolate function."" ... This reverts commit 661be01d9b.	10 years ago
Paul Hinze	567a9b9e06	config: remove missing equals test to fix build ... This is behavior that's covered in the parser now - and the error message is nicer to boot!	10 years ago
James Nugent	87550b2b72	Merge pull request #5263 from uber/b-element-negative ... Error out on negative indices in element()	10 years ago
Paul Hinze	661be01d9b	Revert "core: Add uuid() interpolate function."	10 years ago
Paul Hinze	1e0b8ea478	core: Add uuid() interpolate function. ... Utilizes hashicorp's go-uuid library for proper random seeding setup.	10 years ago
Radek Simko	664ba5f5a6	config: Add new interpolation function - md5	10 years ago
Radek Simko	573d3bd7ab	config: Sort functions mapping alphabetically	10 years ago
Bill Fumerola	c0034e672b	Error out on negative indices in element()	10 years ago
Jeff Zohrab	33d30761dd	Add hint to download modules for new users.	10 years ago
Paul Hinze	9a00675262	Merge pull request #5026 from hashicorp/phinze/destroy-node-copies ... core: Make copies when creating destroy nodes	10 years ago
Paul Hinze	3f72837f4b	core: Make copies when creating destroy nodes ... Fixes an interpolation race that was occurring when a tainted destroy node and a primary destroy node both tried to interpolate a computed count in their config. Since they were sharing a pointer to the _same_ config, depending on how the race played out one of them could catch the config uninterpolated and would then throw a syntax error. The `Copy()` tree implemented for this fix can probably be used elsewhere - basically we should copy the config whenever we drop nodes into the graph - but for now I'm just applying it to the place that fixes this bug. Fixes #4982 - Includes a test covering that race condition.	10 years ago
Radek Simko	4edf782260	Merge pull request #4854 from jfromaniello/add_signum_interpolation ... Add signum interpolation function	10 years ago
Mitchell Hashimoto	5f3de02fa9	remove config/lang, use hashicorp/hil	10 years ago
Radek Simko	ecedcd0032	config: Add base64sha256() function	10 years ago
Colin Hebert	61a40dce13	Update the test file	10 years ago
Colin Hebert	d92d205dd9	rename trim to trimspace	10 years ago
Colin Hebert	d45b7b2ddc	Fix name from strip to trim	10 years ago
Colin Hebert	f5074cd521	Add the trim() interpolation function	10 years ago
José F. Romaniello	c8795b8565	Add signum interpolation function ... This function returns -1 for negative numbers, 0 for 0 and 1 for positive numbers. Useful when you need to set a value for the first resource and a different value for the rest of the resources. Example: `${element(split(",", var.r53_failover_policy), signum(count.index))}`	10 years ago
James Nugent	3bdd1ac8b3	core: Display invalid type in error message ... If a variable type which is invalid (e.g. "stringg") is declared, we now include the invalid type description in the error message to make it easier to track down the source of the error in the source file.	10 years ago
James Nugent	cb6cb8b96a	core: Support explicit variable type declaration ... This commit adds support for declaring variable types in Terraform configuration. Historically, the type has been inferred from the default value, defaulting to string if no default was supplied. This has caused users to devise workarounds if they wanted to declare a map but provide values from a .tfvars file (for example). The new syntax adds the "type" key to variable blocks: ``` variable "i_am_a_string" { type = "string" } variable "i_am_a_map" { type = "map" } ``` This commit does _not_ extend the type system to include bools, integers or floats - the only two types available are maps and strings. Validation is performed if a default value is provided in order to ensure that the default value type matches the declared type. In the case that a type is not declared, the old logic is used for determining the type. This allows backwards compatiblity with previous Terraform configuration.	10 years ago
Paul Hinze	87a9701f91	config: validation error when output is missing value field ... Also lists out invalid keys in errmsg when they are present Closes #4398	10 years ago
Paul Hinze	47b521ebaf	Merge pull request #4745 from hashicorp/b-lifecycle-keys ... config: validate lifecycle keys [GH-4413]	10 years ago
Paul Hinze	911575b7d6	Merge pull request #4747 from hashicorp/b-escaped ... Literals with escaped interpolations work	10 years ago
Mitchell Hashimoto	693736b52a	config: fix tests	10 years ago
Mitchell Hashimoto	f223be15cd	config: eval HEL as long as the result changes [GH-2909]	10 years ago
Mitchell Hashimoto	8e7b0d90e3	config: detect provisioner-only resource in JSON and error [GH-4385]	10 years ago
Mitchell Hashimoto	99fbb91ba2	config: validate lifecycle keys [GH-4413]	10 years ago
Matt Moyer	c17a6ceb2a	Add a sha256(...) interpolation function.	10 years ago
Paul Hinze	0739cf2348	provider/template: fix race causing panic in template_file ... The render code path in `template_file` was doing unsynchronized access to a shared mapping of functions in `config.Func`. This caused a race condition that was most often triggered when a `template_file` had a `count` of more than one, and expressed itself as a panic in the plugin followed by a cascade of "unexpected EOF" errors through the plugin system. Here, we simply turn the FuncMap from shared state into a generated value, which avoids the race. We do more re-initialization of the data structure, but the performance implications are minimal, and we can always revisit with a perf pass later now that the race is fixed.	10 years ago
Joseph Kordish	e1b62c76ad	add sha1 interpolation	10 years ago
Jesse Szwedko	41f9ebc667	Add support for unary operators + and - ... This adds support to the configuration interpolation syntax for + and - as unary operators, specifically to represent negative numbers.	10 years ago
Paul Hinze	b6626eed57	config: friendlier error message on resource arity mismatch ... closes #2072	11 years ago
James Nugent	5ea25363a1	Add regression test for #4069 ... This may be brittle as it makes use of .gitattributes to override the autocrlf setting in order to have an input file with Windows line endings across multiple platforms.	11 years ago
Paul Hinze	d90eb2d88e	config: test replicating #4079 ... Should help cover terraform against regression once https://github.com/hashicorp/hcl/pull/70 lands.	11 years ago