6153 Commits (fd43bc7847c01caa72ca9fec7c19cfb738d4b3a1)

Author	SHA1	Message	Date
Radek Simko	eddcc4d80c	docs: Fix typo (provider arg in data source) (#26802)	6 years ago
Tej-Singh-Rana	832918c65b	website: fixed spelling error (#26758)	6 years ago
timvandamme	fbf267fbfd	website: for_each doesn't implicitly convert to set (#26450) ... The documentation states that an explicit type conversion to set is needed, but it does not say why implicit type conversion does not work. Co-authored-by: Nick Fagerlund <nick@hashicorp.com>	6 years ago
Radek Simko	a413fa7425	Merge pull request #26763 from hashicorp/radeksimko-patch-1 ... docs: fix typo in provider local name	6 years ago
tuathail	33ee8a410c	website: Add note re: private_key configuration to intro (#24463)	6 years ago
Repon Kumar Roy	34549b402b	website: clarify version constraint syntax	6 years ago
Nick Fagerlund	a058b64eb5	website: Index for `element` must be a non-negative integer (#26679) ... * The index must be non-negative integer and added instructions on how to get the last value in the list. * Typo fix Co-authored-by: Nick Fagerlund <nick@hashicorp.com>	6 years ago
Nick Fagerlund	5a4957f141	Typo fix	6 years ago
Nick Fagerlund	a0fee4c380	website: one more provider name typo	6 years ago
Radek Simko	8476c3f13e	docs: fix typo in provider local name	6 years ago
alevinetx	66393bb62e	website: Update module-registry-protocol.html.md (#26639) ... * Update module-registry-protocol.html.md 1: There is a mismatch in the segment labels for the version query URL (system vs provider) 2: There is a discrepancy between the documentation and the actual generated request for retrieving module source code (URL segments 4 vs 3) - There is no segment for "provider" * Update module-registry-protocol.html.md Changed ```:system``` to ```:provider``` for versions and source API URLs	6 years ago
Pam Selle	5f065c76aa	Merge pull request #26710 from aazon/patch-1 ... Small spelling improvement	6 years ago
Pam Selle	bd70bc63eb	Add provider sensitivity propagation experiment ... Rolls back marking attributes providers mark as sensitive to an `experiment` and adds associated docs and adjustments to the upgrade guide.	6 years ago
Alex Litvinenko	1a371c3c49	Small spelling improvement ... It seems that the word `with` is redundant in the following sentence: > For a module with without count or for_each, the address will not...	6 years ago
Kristin Laemmert	b8e3b8036a	backend: remove deprecated atlas backend	6 years ago
Martin Atkins	ddf9635af6	website: Don't claim that things are "very easy" ... We typically try to avoid making subjective, boasty claims in our documentation in recent times, but there remained both some older documentation that we've not recently revised and also some newer examples that are, in retrospect, also perhaps more "boasty" than they need to be. We prefer not to use this sort of boasty language because not everyone using Terraform has the same background and experience, and so what is "easy" or "intuitive" to one person may not be so to another person, and that should not suggest that the second person is in any way wrong or inadequate. In reviewing some of our use of the word "easy" here I tried as much as possible to surgically revise the existing content without getting drawn into a big rewrite, but in some cases the content was either pretty unsalvageable (due to talking about obsolete features that were removed long ago) or required some broader changes to make the result hopefully still get the same facts across. In those cases I've both removed some content entirely or adjusted larger paragraphs. This was not an exhaustive review and so I'm sure there's still plenty of room for similar improvements elsewhere. I also resisted the urge to update some pages that contain outdated information about currently-active features.	6 years ago
Martin Atkins	6a44586a8f	website: Update the CLI commands index page for latest help output ... My initial motivation here was to update the example output from Terraform's top-level help list to match recent updates in the layout and language used. However, while here I took the opportunity to update some dated language that was not consistent with our modern documentation writing style, in particular including a totally unnecessary and potentially-alienating claim that Terraform is "very easy to use". Our modern writing style discourages this sort of "boastful" language and encourages us to focus on the facts at hand.	6 years ago
Arthur Burkart	d4716a69e1	lang/funcs: "anytrue" function ... This is an analog to the "alltrue" function, using OR as the reduce operator rather than AND. This also includes some simplification of the "alltrue" implementation to implement it similarly as a sort of reduce operation with AND as the reduce operator, but with the same effective behavior.	6 years ago
Petros Kolyvas	b1671b2ce1	website: Fix for documentation around local-name conflicts (#26689) ... * Fixes #26684 * Update provider-requirements.html.md Removing additional/extra newlines * Update provider-requirements.html.md And now some trailing spaces. le sigh	6 years ago
James Bardin	ff94be21c2	Merge pull request #26685 from hashicorp/jbardin/separate-loggers ... Separate loggers	6 years ago
James Bardin	eb2d4434c8	logging env variable docs	6 years ago
Petros Kolyvas	bfbdbe9bba	Tool-specific provisioner docs change to red notice box (#26681)	6 years ago
craiggenner	6408533fca	The index must be non-negative integer ... and added instructions on how to get the last value in the list.	6 years ago
Jakson Rodrigues	818029826b	Fixed config argument on example (#26304)	6 years ago
Kerim Satirli	f4790d8f61	updates `description` to reflect endpoint usage (#26278)	6 years ago
Thanonchai	f3fa59f65d	Update config.html.md (#26622) ... * Update config.html.md When reading this page, I couldn't find the list of the "supported backends to the left". They're actually on a different page, so thought I'd update it so that others wouldn't find it confusing like me. If this is ok with you, would it be possible to label this PR with 'hacktoberfest-accepted'? I'm still new to this. If not, I'd be alright. Thank you! * Update config.html.md Swapped the full URL in the link for a relative path Co-authored-by: Petros Kolyvas <petros@hashicorp.com>	6 years ago
Justin Long	0ce11faffd	Clear wording that bucket must pre-exist (#26276) ... Experienced similar issue as https://github.com/hashicorp/terraform/issues/18417 this updates the documentation so that it's more clear a storage bucket must exist prior to configuring the backend.	6 years ago
Jerry Chong	2f091836c9	Modified terraform get command (#26465) ... -Added PATH -Added -no-color option	6 years ago
Diod FR	f0edb192b3	ADD CLI option position for force-unlock command (#26626) ... * ADD CLI option position for force-unlock command * Update force-unlock.html.markdown Made a change to also include the missing [DIR] Co-authored-by: Petros Kolyvas <petros@hashicorp.com>	6 years ago
Martin Atkins	1dc4950bfa	lang/funcs: Rename the base64 character encoding functions ... These were initially introduced as functions with "encode" and "decode" prefixes, but that doesn't match with our existing convention of putting the encoding format first so that the encode and decode functions will group together in a alphabetically-ordered function list. "text" is not really a defined serialization format, but it's a short word that hopefully represents well enough what these functions are aiming to encode and decode, while being consistent with existing functions like jsonencode/jsondecode, yamlencode/yamldecode, etc. The "base64" at the end here is less convincing because there is precedent for that modifier to appear both at the beginning and the end in our existing function names. I chose to put it at the end here because that seems to be our emergent convention for situations where the base64 encoding is a sort of secondary modifier alongside the primary purpose of the function, as we see with "filebase64". (base64gzip is an exception here, but it seems outvoted by the others.)	6 years ago
r0bnet	877399c631	lang/funcs: Functions for encoding text in specific character encodings	6 years ago
Pam Selle	7924117acc	Add note to upgrade guide about provider sensitivity (#26643) ... * Add note to upgrade guide about provider sensitivity Now that sensitivity follows attributes providers mark as sensitive, add this note to the upgrade guide. Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	6 years ago
Alisdair McDiarmid	5e047b0a0b	Merge pull request #26611 from hashicorp/alisdair/sensitive-values-provisioners ... Fixes for sensitive values used as input to provisioners	6 years ago
Alisdair McDiarmid	9d2994ab9b	website: Sensitive values in provisioner config	6 years ago
Pam Selle	02c48f8071	Comment fixing	6 years ago
Martin Atkins	30204ecded	command/cliconfig: Allow development overrides for providers ... For normal provider installation we want to associate each provider with a selected version number and find a suitable package for that version that conforms to the official hashes for that release. Those requirements are very onerous for a provider developer currently testing a not-yet-released build, though. To allow for that case this new CLI configuration feature allows overriding specific providers to refer to give local filesystem directories. Any provider overridden in this way is not subject to the usual restrictions about selected versions or checksum conformance, and activating an override won't cause any changes to the selections recorded in the lock file because it's intended to be a temporary setting for one developer only. This is, in a sense, a spiritual successor of an old capability we had to override specific plugins in the CLI configuration file. There were some vestiges of that left in the main package and CLI config package but nothing has actually been honoring them for several versions now and so this commit removes them to avoid confusion with the new mechanism.	6 years ago
Tony Carmichael	9ff007d322	Update community-index.html.markdown	6 years ago
Tony Carmichael	49a3d14b3b	Update community-index.html.markdown ... Updates to community listings now that registry has been GA for a few months.	6 years ago
James Bardin	ffbdd72196	Merge pull request #26487 from hashicorp/jbardin/shell-escape ... update taint command example	6 years ago
James Bardin	657dd33008	Merge pull request #26557 from remilapeyre/skip-ddl-commands ... Add skip_table_creation and skip_index_creation options to the pg backend	6 years ago
Martin Atkins	e70ab09bf1	command: new cache directory .terraform/providers for providers ... Terraform v0.10 introduced .terraform/plugins as a cache directory for automatically-installed plugins, Terraform v0.13 later reorganized the directory structure inside but retained its purpose as a cache. The local cache used to also serve as a record of specifically which packages were selected in a particular working directory, with the intent that a second run of "terraform init" would always select the same packages again. That meant that in some sense it behaved a bit like a local filesystem mirror directory, even though that wasn't its intended purpose. Due to some unfortunate miscommunications, somewhere a long the line we published some documentation that _recommended_ using the cache directory as if it were a filesystem mirror directory when working with Terraform Cloud. That was really only working as an accident of implementation details, and Terraform v0.14 is now going to break that because the source of record for the currently-selected provider versions is now the public-facing dependency lock file rather than the contents of an existing local cache directory on disk. After some consideration of how to move forward here, this commit implements a compromise that tries to avoid silently doing anything surprising while still giving useful guidance to folks who were previously using the unsupported strategy. Specifically: - The local cache directory will now be .terraform/providers rather than .terraform/plugins, because .terraform/plugins is effectively "poisoned" by the incorrect usage that we can't reliably distinguish from prior version correct usage. - The .terraform/plugins directory is now the "legacy cache directory". It is intentionally _not_ now a filesystem mirror directory, because that would risk incorrectly interpreting providers automatically installed by Terraform v0.13 as if they were a local mirror, and thus upgrades and checksum fetches from the origin registry would be blocked. - Because of the previous two points, someone who _was_ trying to use the legacy cache directory as a filesystem mirror would see installation fail for any providers they manually added to the legacy directory. To avoid leaving that user stumped as to what went wrong, there's a heuristic for the case where a non-official provider fails installation and yet we can see it in the legacy cache directory. If that heuristic matches then we'll produce a warning message hinting to move the provider under the terraform.d/plugins directory, which is a _correct_ location for "bundled" provider plugins that belong only to a single configuration (as opposed to being installed globally on a system). This does unfortunately mean that anyone who was following the incorrectly-documented pattern will now encounter an error (and the aforementioned warning hint) after upgrading to Terraform v0.14. This seems like the safest compromise because Terraform can't automatically infer the intent of files it finds in .terraform/plugins in order to decide automatically how best to handle them. The internals of the .terraform directory are always considered implementation detail for a particular Terraform version and so switching to a new directory for the _actual_ cache directory fits within our usual set of guarantees, though it's definitely non-ideal in isolation but okay when taken in the broader context of this problem, where the alternative would be silent misbehavior when upgrading.	6 years ago
Pam Selle	8f72f4f317	Merge pull request #21936 from tiny-dancer/patch-1 ... Terraform Plan CLI Vars Format	6 years ago
Pam Selle	305c6fc029	Merge branch 'master' into patch-2	6 years ago
Martin Atkins	e1aff2bab0	website: First draft of v0.14 upgrade guide ... The upgrade requirements for this release are considerably more modest than for Terraform v0.13, so this time we just have some notes about a few changes in behavior that may be impactful to some users. This first pass is intended to be included as part of a forthcoming beta testers' guide as we begin the v0.14 beta testing period. We will make further changes to this upgrade guide based on feedback from those who participate in the beta process. Note that this upgrade guide is not intended as release marketing material and so its presentation is focused on addressing concerns users might encounter while upgrading. We'll share highlights from the release in other contexts, such as the changelog and in the product blog.	6 years ago
Rémi Lapeyre	12a0a21c0b	Add skip_table_creation and skip_index_creation options to the pg backend ... Closes https://github.com/hashicorp/terraform/issues/25708	6 years ago
Martin Atkins	0bbbb9c64b	configs: Experimental support for optional object type attributes ... This builds on an experimental feature in the underlying cty library which allows marking specific attribtues of an object type constraint as optional, which in turn modifies how the cty conversion package handles missing attributes in a source value: it will silently substitute a null value of the appropriate type rather than returning an error. In order to implement the experiment this commit temporarily forks the HCL typeexpr extension package into a local internal/typeexpr package, where I've extended the type constraint syntax to allow annotating object type attributes as being optional using the HCL function call syntax. If the experiment is successful -- both at the Terraform layer and in the underlying cty library -- we'll likely send these modifications to upstream HCL so that other HCL-based languages can potentially benefit from this new capability. Because it's experimental, the optional attribute modifier is allowed only with an explicit opt-in to the module_variable_optional_attrs experiment.	6 years ago
Martin Atkins	897cb72b36	website: Initial docs for the new dependency lock file behaviors ... This includes both the main documentation about the lock file itself and changes to related documentation about Terraform commands that interact with the lock file. We will likely continue to update this first pass of documentation as we get feedback and questions during the prerelease period.	6 years ago
Pam Selle	9a9e61ef06	Update docs for output sensitivity change	6 years ago
Pam Selle	cc007a27b7	Merge pull request #26482 from hashicorp/pselle/sensitive-var-nested-docs ... Add sensitive variable docs for nested blocks	6 years ago
James Bardin	c1efe351b2	update taint command example ... Fix the example to match the usual shell style, and add a note about different shells requiring different escaping formats.	6 years ago