21318 Commits (a6f76aa0affc940eb9ecb86c72948ca2768874ba)

 

All Branches   

Search

Author	SHA1	Message	Date
stack72	a6f76aa0af	backend/manta: Manta Backend was not dealing with a ResourceNotFound ... Fixes: #17314 We now deal correctly with the creation of the state file - we were not dealing well with a ResourceNotFound error Now that this has been changed around, we try and create the statefile and if there is an error, we look for an existing statefile - previously this was not the order of operations	8 years ago
Radek Simko	9cef4674c5	Merge pull request #17550 from lrakai/lrakai-patch-module-usage ... Grammar Improvement	8 years ago
Logan Rakai	84637534f4	Grammar Improvement	8 years ago
Martin Atkins	557bc1a349	Update CHANGELOG.md	8 years ago
Martin Atkins	c86a618c0a	Update CHANGELOG.md	8 years ago
James Bardin	95c39d0c0b	Merge pull request #17548 from hashicorp/jbardin/GH-17368 ... ignore errors interpolating RawCount during apply	8 years ago
James Bardin	a2718e4f79	ignore errors interpolating RawCount during apply ... If a count field references another count field which is interpolated but is attached to a resource already in the state, the result of that first interpolation will be lost when a plan is serialized. This is because the result of the first interpolation is stored directly in the module config, in an unexported config field. This is not a general fix for the above situation, which would require refactoring how counts are handles throughout the config. Ignoring the error works, because in most cases the count will be properly handled during the resource's interpolation.	8 years ago
James Bardin	f3d1fb3aff	failing test for interpolated count from plan ... An interpolated count value that is determined during plan, is lost during plan serialization, causing apply to fail when the interpolation string can't be evaluated.	8 years ago
James Bardin	bb8f859113	Merge pull request #17545 from hashicorp/jbardin/remote-state-environment ... don't let default workspace override environment	8 years ago
James Bardin	e011dd95f3	don't let default workspace override environment ... The workspace attribute should only override the environment if it's not the default value.	8 years ago
Martin Atkins	441e62748c	Update CHANGELOG.md	8 years ago
Martin Atkins	b94da25919	Update CHANGELOG.md	8 years ago
Martin Atkins	6aefa5835c	Merge #17218: Add -auto-approve to "terraform destroy" for consistency	8 years ago
Martin Atkins	5661ab5991	configs: allow full type constraints for variables ... Previously we just ported over the simple "string", "list", and "map" type hint keywords from the old loader, which exist primarily as hints to the CLI for whether to treat -var=... arguments and environment variables as literal strings or as HCL expressions. However, we've been requested before to allow more specific constraints here because it's generally better UX for a type error to be detected within an expression in a calling "module" block rather than at some point deep inside a third-party module. To allow for more specific constraints, here we use the type constraint expression syntax defined as an extension within HCL, which uses the variable and function call syntaxes to represent types rather than values, like this: - string - number - bool - list(string) - list(any) - list(map(string)) - object({id=string,name=string}) In native HCL syntax this looks like: variable "foo" { type = map(string) } In JSON, this looks like: { "variable": { "foo": { "type": "map(string)" } } } The selection of literal processing or HCL parsing of CLI-set values is now explicit in the model and separate from the type, though it's still derived from the type constraint and thus not directly controllable in configuration. Since this syntax is more complex than the keywords that replaced it, for now the simpler keywords are still supported and "list" and "map" are interpreted as list(any) and map(any) respectively, mimicking how they were interpreted by Terraform 0.11 and earlier. For the time being our documentation should continue to recommend these shorthand versions until we gain more experience with the more-specific type constraints; most users should just make use of the additional primitive type constraints this enables: bool and number. As a result of these more-complete type constraints, we can now type-check the default value at config load time, which has the nice side-effect of allowing us to produce a tailored error message if an override file produces an invalid situation; previously the result was rather confusing because the error message referred to the original definition of the variable and not the overridden parts.	8 years ago
Seth Vargo	12f8c90a51	website: Recommend SVG instead of PNG for graph output	8 years ago
Martin Atkins	c05a1050fc	configs: Disable deprecation warning for quoted keywords/references ... Although we do still consider these deprecated for 0.12, we'll defer actually generating warnings for them until a later minor release so that module authors can retain their quoted identifiers for a period after 0.12 release for backward-compatibility with Terraform 0.11.	8 years ago
Martin Atkins	a26ff56f01	configs: highlight resource name in diags when invalid ... Previously we were erroneously highlighting the resource type name instead.	8 years ago
James Bardin	f825a2118b	Merge pull request #17513 from hashicorp/jbardin/GH-17509 ... Check for nil config in node_resource_refresh	8 years ago
Martin Atkins	3cec7dc595	Merge #17533: Update "HCL2" and cty dependencies	8 years ago
Martin Atkins	7549ce15f0	configs: update values file invalid syntax test for new HCL behavior ... The error-handling behavior of the HCL parser was improved, which causes the number of diagnostics and the diagnostics messages to be different in cases where a block-like introduction is given but without any following body.	8 years ago
Martin Atkins	59a49c6b3f	vendor: update hcl2 and cty ... This is largely minor bugfixes for issues found since we last updated the vendoring. There are some new features here that Terraform is not yet using and thus present little risk. In particular this includes the HCL-JSON spec change where arrays can now be used at any level in a block label structure, to allow for preserving the relative order of blocks.	8 years ago
James Bardin	5727d33352	Merge pull request #17531 from hashicorp/jbardin/null-output ... filter null output values from state	8 years ago
James Bardin	13433687cb	filter null output values from state ... While null values should not normally appear in a state file, we should filter the values rather than crash.	8 years ago
Paul Tyng	a61b40c7a2	Merge pull request #17517 from ivanovteo/ivanovteo/docs-providers-small-typo ... Trivial documentation fix	8 years ago
Andrei Ivanov	53110e5c1f	- fixed a trivial typo	8 years ago
James Bardin	7fd6f97899	Check for nil config in node_resource_refresh ... While not normally possible, manual manipulation of the state and config can cause us to end up with a nil config in evalTreeManagedResourceNoState. Regardless of how it got here, we can't ever assume the Config field is not nil, and EvalInterpolate happily accepts a nil RawConfig	8 years ago
Martin Atkins	ea50f455ed	Update CHANGELOG.md	8 years ago
Kristiyan Nikolov	999f9096c1	provisioner/local-exec: Allow passing environment variables	8 years ago
Chris Griggs	6f98b4d4be	website: two more community providers	8 years ago
Anthony Galea	664391c254	website: fix various typos	8 years ago
Paul Tyng	26058acdef	Merge pull request #17467 from paultyng/pt/useragent ... Standardize on User-Agent usage for registry, provider downloads, etc.	8 years ago
Chris Griggs	1da2152482	website: Link to MongoDB Atlas community provider	8 years ago
Paul Tyng	c868092d2d	Standardize http.Client creation with User-Agent	8 years ago
Paul Tyng	344e8fca05	Relax typing to allow for http.RoundTripper	8 years ago
Nick Fagerlund	66ff8f8bed	website: Deprecation notes about "terraform push" ... Also: - In the getting started guide, the TFE content was all tailored to the older run-locally workflow. I've replaced it with some brief explanation and a link to the dedicated TFE getting started guide. - Fixed a sidebar link glitch in the configuration section. (Both "Terraform" and "Terraform Enterprise" were marked as active if you were on the TFE page.) - Renamed the "Terraform Enterprise" page "Terraform Push." (Some people have gotten confused and landed on this page when trying to set up the `atlas` remote backend.)	8 years ago
James Bardin	dc8036636a	Merge pull request #17422 from hashicorp/jbardin/state-locking ... Add StateLocker interface to backend operations	8 years ago
James Bardin	2b97585d46	improve clistate.Locker docs	8 years ago
azban	3f2f07d5d0	website: don't document unimplemented salt-masterless grains_file	8 years ago
Martin Atkins	fe3a5f100d	Update CHANGELOG.md	8 years ago
Uriel Corfa	07a20365de	cli: "terraform state list" -id argument ... A new -id option to "terraform state list" which constraints the output of the command to resources whose id is equal to the flag value.	8 years ago
James Bardin	81dc23c65d	Merge pull request #17434 from NikkeiFTLearning/saltstack-race-problem ... fix ssh problem with communicator.Retry	8 years ago
Paweł Socha	be8d39210d	Wait for ssh connection	8 years ago
Brian Flad	7bb2c17630	Merge pull request #17428 from hashicorp/v-terraform-provider-aws-v1.10.0 ... Deps: Bump terraform-provider-aws@v1.10.0 and aws-sdk-go@v1.12.75	8 years ago
Paweł Socha	627bb24ea6	fix ssh problem with communicator.Retry	8 years ago
Brian Flad	8ee936a068	Deps: Bump terraform-provider-aws@v1.10.0 and aws-sdk-go@v1.12.75	8 years ago
James Bardin	bdd475e149	use the new clistate.Locker in commands ... Use the new StateLocker field to provide a wrapper for locking the state during terraform.Context creation in the commands that directly manipulate the state.	8 years ago
James Bardin	e9a76808df	create clistate.Locker interface ... Simplify the use of clistate.Lock by creating a clistate.Locker instance, which stores the context of locking a state, to allow unlock to be called without knowledge of how the state was locked. This alows the backend code to bring the needed UI methods to the point where the state is locked, and still unlock the state from an outer scope. Provide a NoopLocker as well, so that callers can always call Unlock without verifying the status of the lock. Add the StateLocker field to the backend.Operation, so that the state lock can be carried between the different function scopes of the backend code. This will allow the backend context to lock the state before it's read, while allowing the different operations to unlock the state when they complete.	8 years ago
Martin Atkins	9cf5350590	Update CHANGELOG.md	8 years ago
James Bardin	12bda53558	Revert "create clistate.Locker interface" ... This reverts commit e88bd74bb7.	8 years ago
James Bardin	626c5ed672	Revert "add backend.Operation.StateLocker" ... This reverts commit d3f7edeb27.	8 years ago