terraform

Commit Graph

Author	SHA1	Message	Date
James Bardin	e024960c74	Revert "filter nulls when shimming a config" This reverts commit `97bde5467c`.	7 years ago
James Bardin	f5395bd98a	validate null values in shimmed configs A list-like attribute containing null values will present a list to helper/schema with nils, which can cause panics. Since null values were not possible in configuration before HCL2 and not supported by the legacy SDK, return an error to the user.	7 years ago
James Bardin	7ced46425e	Merge pull request #20906 from hashicorp/jbardin/grpc-recv-limit increase grpc recv limit	7 years ago
James Bardin	2ebc2beda0	add 3rd param to mock call	7 years ago
James Bardin	746aac8bda	increase grpc recv limit Some providers may generate quite large schemas, and the internal default grpc response size limit is 4MB. 64MB should cover most any use case, and if we get providers nearing that we may want to consider a finer-grained API to fetch individual resource schemas.	7 years ago
James Bardin	34358254ec	Merge pull request #20904 from hashicorp/jbardin/filter-shim-nulls filter nulls when shimming a config	7 years ago
James Bardin	97bde5467c	filter nulls when shimming a config Nulls can't exist in HCL, and the legacy sdk will panic when encountering them. The map shim already did this, just copy the same pattern in the list case.	7 years ago
Chris Griggs	16778fea92	Merge pull request #20887 from cgriggs01/cgriggs01-fix-typo [Website] Update provider name	7 years ago
Martin Atkins	6c5819f910	configs/configupgrade: Prefer block syntax for list-of-object attributes In order to preserve pre-v0.12 idiom for list-of-object attributes, we'll prefer to use block syntax for them except for the special situation where the user explicitly assigns an empty list, where attribute syntax is required in order to allow existing provider logic to differentiate from an implicit lack of blocks.	7 years ago
cgriggs01	cfd271a040	update provider name	7 years ago
Kristin Laemmert	39ef97beff	website: adding examples of complex variables on the command line (#20871 )	7 years ago
Bruno Tavares	6bad319187	go.mod: remove unneeded indirect for "mgo" and "gocheck" We don't appear to actually need to constrain these, and removing these decls may help avoid the need for `bzr` to install all the dependencies.	7 years ago
Martin Atkins	1f9a8aa75e	Update CHANGELOG.md	7 years ago
Frederic	0f1f504c22	command/format: indicate in diff when adding an attribute forces replacement	7 years ago
James Bardin	e893bae5da	Merge pull request #20874 from hashicorp/jbardin/shim-unknown-values Better handling of unknowns in sdk shims	7 years ago
James Bardin	64c76be804	fixup lost collections containing unknowns It turns out that collections containing only unknowns could be lost, meaning there wasn't a direct correlation between the unknown and null value which would have otherwise been restored.	7 years ago
James Bardin	6868ddd085	don't set NewRemoved values as empty strings NewRemoved diff values were somtimes left in maps and lists.	7 years ago
James Bardin	86e30add98	fix unknowns added to maps by schemaMap The legacy diff process inserts unknown values into an optional+computed map. Fix these up in post-plan normalization process, by looking for known strings that were changed to unknown.	7 years ago
James Bardin	009df443f7	restore lost unknowns during a planned update. Because schema.ResourceDiff can't differentiate between unknown values and new computed values, unknowns can be lost during an update. If a planned value converted an unknown to a null, restore the unknown so that it can be correctly replaced in the final plan.	7 years ago
James Bardin	8b9fa6d05f	add test provider coverage around unknown vals	7 years ago
Sander van Harmelen	137974c4a8	Update CHANGELOG.md	7 years ago
Sander van Harmelen	b94ddab3a7	Merge pull request #20857 from hashicorp/svh/b-console-vars backend/remote: correctly load remote variables	7 years ago
Kristin Laemmert	da52170797	configupgrade: fix test (#20863 )	7 years ago
Pam Selle	4c1bb8abd7	Update CHANGELOG.md	7 years ago
Kristin Laemmert	1baa1b907e	configs/configupgrade: detect invalid resource names and print a TODO (#20856 ) * configs/configupgrade: detect invalid resource names and print a TODO message In terraform 0.11 and prior it was possible to start a resource name with a number. This is no longer valid, as the resource name would would be ambiguous with number values in HCL expressions. Fixes #19919 * Update configs/configupgrade/test-fixtures/valid/invalid-resource-name/want/resource.tf Co-Authored-By: mildwonkey <mildwonkey@users.noreply.github.com>	7 years ago
Martin Atkins	003317d7c8	lang: Detect references when a list/set attr is defined using blocks For compatibility with documented patterns from existing providers we are now allowing (via a pre-processing step) any attribute whose type is a list-of-object or set-of-object type to optionally be assigned using one or more blocks whose type is the attribute name. The pre-processing functionality was implemented in previous commits but we were not correctly detecting references within these blocks that are, from the perspective of the primary schema, invalid. Now we'll use an alternative implementation of variable detection that is able to apply the same schema rewriting technique we used to implement the transform and thus can find all of the references as if they were already in their final locations.	7 years ago
Martin Atkins	8746e9e8ad	lang/blocktoattr: ExpandedVariables function Because we handle FixUpBlockAttrs after dynamic block expansion, when resolving variables we unfortunately need to consider the possibility of both dynamic block expansion _and_ the block attrs fixup. To accommodate this we have a variant of dynblock.VariablesHCLDec that instead walks using the configschema.Block representation of the schema and applies the same opportunistic schema rewrite used by FixUpBlockAttrs at each body encountered during the walk.	7 years ago
Martin Atkins	b35bc255d2	vendor: go get github.com/hashicorp/hcl2@master This gives us an extra hook in the dynblock variables analysis that should allow us to also make it subject also to the lang/blocktoattr fixup, to ensure we'll find all the references in spite of these various pre-processing wrappers.	7 years ago
Martin Atkins	87786484ea	lang/eval: Apply attr-as-nested-block fixup in EvalBlock For any block content we evaluate dynamically via this API, we'll make a special allowance for users to optionally write members of a list attribute instead as a sequence of nested blocks, thus allowing some existing provider features that were assuming this capability to continue to support it after v0.12. This should not be used for any new provider features, and should ideally be eventually phased out so that there aren't two similar-but-slightly-different syntaxes for saying the same thing.	7 years ago
Martin Atkins	6dcf8195b8	lang/blocktoattr: Selectively allow block syntax to be used for attributes This preprocessing step allows users to use nested block syntax to specify elements of an attribute that is defined as being a list or set of an object type. This restores part of the unintended flexibility permitted in Terraform v0.11 so that we can work around a few tricky edges where provider implementations were relying on Terraform's failure to validate this in earlier versions. For any body that is pre-processed using this new helper, we will recognize when a configuration author uses nested block syntax with a name that is specified in the schema as an attribute of a suitable type and tweak the schema just in time before decoding to expect that usage and then fix up the result on the way out to conform to the original schema. Achieving this requires an abstraction inversion because only Terraform's high-level schema has enough information to decide how to rewrite the incoming low-level schema. We must therefore here implement HCL's lowest-level API interface in terms of the higher-level abstractions of hcldec and Terraform's configschema. Because of the abstraction inversion this fixup mechanism cannot be used generally for arbitrary HCL bodies but we can use it carefully inside the lang package where its own API can guarantee the necessary invariants for this to work.	7 years ago
Pam Selle	d1c1bc6cdb	Merge pull request #20853 from pselle/err-handling-registry-unresponsive Add friendly error for when registry unresponsive	7 years ago
Sander van Harmelen	39a95e4222	backend/remote: correctly load remote variables When using `terraform console` in combination with the remote backend, variables defined in Terraform Enterprise were load loaded correctly.	7 years ago
Kristin Laemmert	931851ca82	update terraform-config-inspect (#20852 )	7 years ago
Sander van Harmelen	86164c0bb4	Merge pull request #20843 from hashicorp/svh/f-force-push backend/local: preserve serial and lineage on failure	7 years ago
Pam Selle	ff7245f27c	Add status link to make message more helpful	7 years ago
Chris Griggs	c69cc88c8b	Merge pull request #20848 from cgriggs01/cgriggs01-jdcloud [Website] Add JDcloud provider	7 years ago
cgriggs01	fc47a78e60	add jdcloud provider links	7 years ago
Pam Selle	d72456d188	Add friendly error for when registry unresponsive If the registry is unresponsive, you will now get an error specific to this, rather than a misleading "provider unavailable" type error. Also adds debug logging for when errors like this may occur	7 years ago
Sander van Harmelen	21cca34716	Fixup the docs for WriteStateForMigration	7 years ago
Sander van Harmelen	57f6e01830	backend/local: preserve serial and lineage on failure When failing to write the state, the local backend writes the state to a local file called `errrored.tfstate`. Previously it would do so by creating a new state file which would use a new serial and lineage. By exorting the existing state file and directly assigning the new state, the serial and lineage are preserved.	7 years ago
Martin Atkins	f302747077	website: Additional explanation for cidrsubnet function Some users are not accustomed to thinking of IP addresses in a bitwise fashion, so the hope here is to give enough of an introduction to that way of thinking for the reader to understand what the "newbits" and "netnum" arguments represent.	7 years ago
James Bardin	a63c1af8e0	Merge pull request #20826 from hashicorp/jbardin/validate-connection merge connection blocks for validation	7 years ago
James Bardin	3c8b46fffe	merge connection blocks for validation The resource connection block was not being validated. Merge the two bodies, with the provider as the override, before validation.	7 years ago
Kristin Laemmert	d5bb09b13b	command/show: refresh is required to show remote state (#20818 )	7 years ago
Alex McLarty	4b9a764eb1	website: Fix typo in null_resource.html.markdown (#20817 ) Fix typo in null_resource.html.markdown	7 years ago
Nick Fagerlund	d0b7771634	website: Simplify wording for split built-in function (#20803 ) The definition of split was referring the built-in function join. However, join is just one of the ways a string might have been created, and this could cause confusion.	7 years ago
Nick Fagerlund	b32cce9637	website: Fix contradictory description of remote state `outputs` object	7 years ago
Nick Fagerlund	499ccd42bf	website: fix broken markdown in modules/composition	7 years ago
Martin Atkins	1f241f8f83	docs: Some updates to the architecture summary This doc was originally written in the middle of Terraform v0.12 development while some refactoring was already in progress. Here we update those parts to refer to where the relevant functionality finally landed, and also update some things that we did not anticipate changing at the time but ended up having to be changed during the v0.12 development anyway.	7 years ago
Martin Atkins	18c88f5a41	docs: Import some existing docs to bootstrap the codebase docs section For a while now we've been gathering some codebase-level docs that felt out-of-place on the main Terraform website (since they are about the implementation, not usage) but we had no existing suitable place to put them. In order to make this information more available (and, hopefully, more likely to stay up-to-date as we change things), here we'll establish the "docs" directory as a place to keep documentation aimed at those who are working on code changes to the Terraform Core codebase. User-oriented docs should never appear in this directory. The Terraform website is always the better place for those. The set of docs here is rudimentary to start and we'll see if it makes sense to expand and reorganize it over time based on the experience with having these initial docs available.	7 years ago

1 2 3 4 5 ...

23855 Commits (e024960c745f0a464cb081d04765d93f94deaba0) All Branches Search

23855 Commits (e024960c745f0a464cb081d04765d93f94deaba0)

All Branches