23855 Commits (e024960c745f0a464cb081d04765d93f94deaba0)

 

All Branches   

Search

Author	SHA1	Message	Date
James Bardin	657dddceab	Merge pull request #20799 from hashicorp/jbardin/tests-force-new ... add (forces new resource) to provider test diffs	7 years ago
Nick Fagerlund	4200b0b2c5	website: Use bullet lists in smaller provider lists, too ... These are small enough that using multi-columns would just get in the way, but might as well style them similarly.	7 years ago
Nick Fagerlund	b14b967fb7	website: Fix some alphabetization in provider lists	7 years ago
Nick Fagerlund	33118b9b0c	website: List providers vertically instead of horizontally ... This should make it easier to find items alphabetically, and it DEFINITELY makes it easier to update.	7 years ago
Vangelis Katsikaros	94463894ec	website: "map" a real resource to configuration, not "attach" (#17912) ... In the terraform state documentation the verb "map" is widely used to describe the relationship between an item in the state and in the real world whereas the verb "attach" is not used anywhere.	7 years ago
Nick Fagerlund	428a2c05e7	website: Expand output values docs (#20790) ... For 0.11 I just specified the naming rules; for 0.12, I added some info about referencing values and tightened up the layout of the optional arguments. This commit also syncs up descriptions of `depends_on`.	7 years ago
Nick Fagerlund	53cff99f84	website: Add `workspace show` command to sidebar nav (#20800)	7 years ago
Guillaume Dupin	4b8d11e2de	Create commands/workspace/show.html.md (#18355) ... Add documentation for `terraform workspace show` command	7 years ago
James Bardin	bb62aba651	add (forces new resource) to provider test diffs ... Add the (forces new resource) annotation to the diff output for provider tests failures when we can. This helps providers narrow down what might be triggering changes when encountering test failures with the new SDK.	7 years ago
Nick Fagerlund	c06674bac7	website: Clarify that example S3 policy is for an IAM entity (#20791)	7 years ago
James Bardin	2e15f6f585	Merge pull request #20797 from hashicorp/jbardin/update-goplugin ... udpate go-plugin	7 years ago
James Bardin	11dba9f86a	udpate go-plugin	7 years ago
Nick Fagerlund	cb4f3004da	website: Fix several spelling errors	7 years ago
Nick Fagerlund	740aff3899	website: Update options for graph command ... 'legacy' doesn't seem to be a thing anymore, and we were missing some of the other values for -type. Also -no-color doesn't seem to be relevant to this command.	7 years ago
Nick Fagerlund	b61e50be13	website: Use a normal file-based template in example, and expand the explanation of $${thing}	7 years ago
Lars Francke	db6ec472ef	website: Fix documentation glitch and add note about double "$" ... 1. The double "$" in the template confuses readers 2. As far as I can tell the variable "count" is not used either in this example (it is in the next example though)	7 years ago
Martin Atkins	2a64a00983	core: Upgrade flatmap to JSON when dynamic attributes are present ... When a resource type schema includes dynamically-typed attributes we can't do any automatic conversion from flatmap to JSON because we don't know how to interpret the keys that start with the dynamically-typed attribute's prefix. To work around that, we'll instead just ask the SDK to do a no-op upgrade (current and target versions are the same) which will convert from flatmap to JSON using the SDK's own logic as a side-effect. This situation should rarely arise in real-world use, but it ends up being very important for the helper/resource provider test harness because it is forced to lower the state back to flatmap repeatedly after every step in order to run legacy checking and processing code.	7 years ago
Martin Atkins	135121562e	helper/plugin: Implement Schema.SkipCoreTypeCheck ... The previous commit added this flag but did not implement it. Here we implement it by adjusting the shape of schema we return to Terraform Core to mark the attribute as untyped and then ensure that gets handled correctly on the SDK side.	7 years ago
Martin Atkins	7f860dc83e	helper/schema: Schema.SkipCoreTypeCheck flag ... When running in v0.12-and-higher mode, this will cause the SDK to report the type of the attribute as "any", effectively skipping type checking on the Core side altogether and checking only in the SDK and provider code. The practical impact of this is to restore the v0.11-style checking behavior of allowing object values to be missing certain attributes as long as they are marked as optional in the schema. The SDK can do this because it uses a unified schema model for both object values and nested blocks, while Terraform Core only supports the idea of "optional" when talking about attributes in nested blocks. This is a continuation of the pile of workarounds that also includes the ConfigMode and AsSingle fields, allowing providers to selectively opt out of new v0.12 behaviors in situations where they conflict with decisions made in the design of the providers in our old world where Terraform Core delegated _all_ validation to providers. This is designed as an opt-in so that we can limit its impact only to specific cases where it's needed and minimize the risk of regressions elsewhere. Providers should use this sparingly only in situations where prevailing usage disagrees with the new expectations of Terraform Core in v0.12. This commit only adds the flag, and does not implement any behavior for it yet. That means this commit can exist in both the v0.11 and v0.12 codebases, allowing for API compatibility. A subsequent commit for v0.12 (not included in v0.11) will then implement this behavior.	7 years ago
Justin Downing	1e32ae243c	grammatical updates to comments and docs (#20195)	7 years ago
Sander van Zoest	42305e62ea	website: Fix a typo in null_resource provisioner page description (#19928)	7 years ago
Kim Ngo	479964ad66	Merge pull request #20781 from findkim/registry-checksum ... plugin/discovery: verify registry checksum	7 years ago
Justin Clark	7af7fb3f71	website: access_token is not required in `atlas` backend (#20222)	7 years ago
findkim	161fe47b34	plugin/discovery: improve providery discovery verification errors	7 years ago
findkim	2726282307	plugin/discovery: add context for provider discovery verification	7 years ago
Daniel Schroeder	b29102dbc6	website: Add TF_IN_AUTOMATION to environment variables page (#19721) ... * Adds TF_IN_AUTOMATION description Blatantly copied from https://learn.hashicorp.com/terraform/development/running-terraform-in-automation since it is missing on the [env var page](https://www.terraform.io/docs/configuration/environment-variables.html). * Update website/docs/commands/environment-variables.html.md Co-Authored-By: udondan <udondan@users.noreply.github.com>	7 years ago
findkim	1a32617d5e	plugin/discovery: verify checksum matches Registry response	7 years ago
Brian Flad	2e6c316fc9	Merge pull request #20760 from hashicorp/mar19_s3_path_style ... website: document s3 backend's force_path_style argument	7 years ago
Alvaro Miranda Aguilera	ac0bdb7f21	website: fix heredoc syntax in chef.html.markdown (#19739) ... remove - from EOF	7 years ago
Martin Atkins	373f94fe89	vendor: go get github.com/zclconf/go-cty/cty@master ... This includes a fix to prevent unintentional infinite recursion when trying to unify multiple object types to a single type for conversion to list(any). Sadly I wasn't able to reproduce the problem as reported (in #20728), so therefore I wasn't able to write a Terraform test for it, but I have confirmed that the cty behavior here was incorrect anyway (recursively calling the same function we're already in with the same arguments is clearly not productive) and so this change will allow whatever situation that was to terminate with a type conversion error, rather than causing a stack overflow. It's likely that there is another bug lurking under this, since the problematic code here was supposed to be unreachable, but avoiding the crash is the priority for now. If the problem re-surfaces then it should at least be an error message with some additional context about what the goal of the caller was. This also includes an unrelated fix for the gocty package, which doesn't affect Terraform because it makes very little use of that package.	7 years ago
Nikolai Vavilov	01e26e337e	website: add missing article (#19368)	7 years ago
Nathan Dataguake Basanese	32daeec29d	website: clean up `terraform destroy` output example (#20099)	7 years ago
Martin Atkins	2632ccc5d3	Update CHANGELOG.md	7 years ago
Martin Atkins	096b1bb87b	lang/funcs: Port the "reverse" function from the old functions set ... This has the same functionality as the "reverse" function that was implemented in the "config" package, but adapted to the new language type system.	7 years ago
Sargun Dhillon	ebb551b86f	config: new "reverse" interpolation function ... It reverses a list.	7 years ago
Martin Atkins	2f2897f01a	Update CHANGELOG.md	7 years ago
Stefan Schmidt	3ca1253796	backend/gcs: Mark the unused attributes project and region as removed. ... These two attributes are not used since aec45e6967.	7 years ago
Martin Atkins	2b1e650df2	lang/funcs: Fix out-of-bounds ArgError in templatefile function ... The templatefile function only has two arguments, so ArgErrorf can be called with only zero or one as the argument index. If we are out of bounds then HCL itself will panic trying to build the error message for this call when called as an HCL function. Unfortunately there isn't really a great layer in Terraform to test for this class of bug systematically, because we are currently testing these functions directly rather than going through HCL to do it. For the moment we'll just live with that, but if we see this class of error arise again we might consider either reworking the tests in this package to work with HCL expression source code instead of direct calls or adding some additional tests elsewhere that do so.	7 years ago
Martin Atkins	a4df1ba6d1	Update CHANGELOG.md	7 years ago
Martin Atkins	e918fa83ec	command/format: Don't panic when item removed from list of objects ... Due to these tests happening in the wrong order, removing an object from the end of a sequence of objects would previously cause a bounds-check panic. Rather than a more severe rework of the logic here, for now we'll just introduce an extra precondition to prevent the panic. The code that follows already handles the case where there _is_ no new object (i.e. the "old" object is being deleted) as long as we're able to pass through this type-checking logic. The new "JSON list of objects - removing item" test covers this problem by rendering a diff for an object being removed from the end of a list of objects within a JSON value.	7 years ago
Martin Atkins	35df450dc0	helper/resource: Preserve provider address when shimming to old state ... It's important to preserve the provider address because during the destroy phase of provider tests we'll use the references in the state to determine which providers are required, and so without this attempts to override the provider using the "provider" meta-argument can cause failures at destroy time when the wrong provider gets selected. (This is particularly acute in the google-beta provider tests because that provider is _always_ used with provider = "google-beta" to override the default behavior of using the normal "google" provider.)	7 years ago
Sander van Harmelen	a710447eaf	website: clarify behavior and version support for remote backend (#20739) ... * docs: elaborate on supported remote backend versions This PR adds a few lines to the docs to indicate which commands are supported by what version of the remote backend and it makes a recommendation about which version to use. * Clarify remote state storage w/ TFE [skip ci] Specifically, that this is the backend to use with remote state (all tiers) and Free-Tier vs. Enterprise tiers differ in remote operations * website: Arrange remote backend info differently	7 years ago
Nick Fagerlund	88fcb67cc7	website: document s3 backend's force_path_style argument ... Added in fb6b349e58	7 years ago
Tomas Chmelevskij	036a1e259e	website: Typo fix (#20629)	7 years ago
PenelopeFudd	cf0ed422b2	website: Added missing doublequotes. (#20696)	7 years ago
Paul Tyng	eb582744df	Merge pull request #20738 from hashicorp/paultyng-patch-1 ... Fix documented limitations on Elem for TypeMap	7 years ago
Martin Atkins	50a101afbd	lang: Consider "dynamic" blocks when resolving references ... The hcldec package has no awareness of the dynamic block extension, so the hcldec.Variables function misses any variables declared inside dynamic blocks. dynblock.VariablesHCLDec is a drop-in replacement for hcldec.Variables that _is_ aware of dynamic blocks, returning all of the same variables that hcldec would find naturally plus also any variables used inside the dynamic block "for_each" and "labels" arguments and inside the nested "content" block.	7 years ago
Martin Atkins	838a42d218	vendor: go get github.com/hashicorp/hcl2@master ... This includes improved functionality for HCL's "dynamic block extension", which will allow us (in a subsequent commit) to properly detect dependencies inside nested "dynamic" blocks, where currently they get missed. For this commit though, we just upgrade HCL to a version that includes it and make a small change to our "lang" package to align with an upstream renaming.	7 years ago
HashedDan	a2c91ca582	Docs: reference resource by index, fixes #18184	7 years ago
Martin Atkins	04f3766fd9	website: Indicate v0.12-only content ... We have released the v0.12-oriented content to the website early in order to support the beta process, but in some places we neglected to explicitly mark features or content as being v0.12-only. Here we add explicit markers to the main cases we've seen where readers have reported confusion, along with some other tweaks in similar vein.	7 years ago