1292 Commits (f-func-expandnull)

Author	SHA1	Message	Date
Martin Atkins	5f5432e8ea	website: v0.15 upgrade guide for sensitive resource attributes (#28355) ... * website: v0.15 upgrade guide for sensitive resource attributes Our earlier draft of this guide didn't include a section about the stabilization of the "provider_sensitive_attrs" language experiment. This new section aims to address the situation where a module might previously have been returning a sensitive value without having marked it as such, and thus that module will begin returning an error after upgrading to Terraform v0.15. As part of that, I also reviewed the existing documentation about these features and made some edits aiming to make these four different sections work well together if users refer to them all at once, as they are likely to do if they follow the new links from the upgrade guide. I aimed to retain all of the content we had before, but some of it is now in a new location. In particular, I moved the discussion about the v0.14 language experiment into the upgrade guide, because it seems like a topic only really relevant to those upgrading from an earlier version and not something folks need to know about if they are using Terraform for the first time in v0.15 or later. * minor fixups Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
Martin Atkins	140c613ae8	lang/funcs: "one" function ... In the Terraform language we typically use lists of zero or one values in some sense interchangably with single values that might be null, because various Terraform language constructs are designed to work with collections rather than with nullable values. In Terraform v0.12 we made the splat operator [*] have a "special power" of concisely converting from a possibly-null single value into a zero-or-one list as a way to make that common operation more concise. In a sense this "one" function is the opposite operation to that special power: it goes from a zero-or-one collection (list, set, or tuple) to a possibly-null single value. This is a concise alternative to the following clunky conditional expression, with the additional benefit that the following expression is also not viable for set values, and it also properly handles the case where there's unexpectedly more than one value: length(var.foo) != 0 ? var.foo[0] : null Instead, we can write: one(var.foo) As with the splat operator, this is a tricky tradeoff because it could be argued that it's not something that'd be immediately intuitive to someone unfamiliar with Terraform. However, I think that's justified given how often zero-or-one collections arise in typical Terraform configurations. Unlike the splat operator, it should at least be easier to search for its name and find its documentation the first time you see it in a configuration. My expectation that this will become a common pattern is also my justification for giving it a short, concise name. Arguably it could be better named something like "oneornull", but that's a pretty clunky name and I'm not convinced it really adds any clarity for someone who isn't already familiar with it.	5 years ago
Víctor Felipe Godoy Hernández	a9487c7674	Fix yamldecode example from json to yaml (#28220) ... * Fix yamldecode example from json to yaml * inline yaml example	5 years ago
Martin Atkins	f47c4efb1b	website: Dynamic blocks can for_each any collection type ... We previously added a hint to both resource for_each and dynamic blocks about using the "flatten" and "setproduct" situations to construct suitable collections to repeat over. However, we used the same text in both places which ended up stating that dynamic blocks can only accept map or set values, which is a constraint that applies to resource for_each (because we need to assign a unique identifier to each instance) and not to dynamic blocks (which don't have any uniqueness enforced by Terraform Core itself). To remove that contradiction with the text above which talks about what is valid here, I've just generalized this to say "collection", because the primary point of this paragraph is the "one element per desired nested block" part, not specifically what sort of collections are permitted in this location. (Text further up describes the supported types.)	5 years ago
Robin Norwood	e3bd661470	Merge pull request #28164 from hashicorp/rln-add-resource-targeting-tutorial-callout ... Add callout to resource targeting tutorial	5 years ago
Matthew Frahry	15779013da	backend/azurerm: Bug fixes and updated dependencies #28181	5 years ago
Judith Malnick	75fbbe8065	clarify version that pull upgrades local state to (#28204)	5 years ago
Martin Atkins	6f35c2847b	command: Reorganize docs of the local backend's legacy CLI options ... We have these funny extra options that date back to before Terraform even had remote state, which we've preserved along the way by most recently incorporating them as special-case overrides for the local backend. The documentation we had for these has grown less accurate over time as the details have shifted, and was in many cases missing the requisite caveats that they are only for the local backend and that backend configuration is the modern, preferred way to deal with the use-cases they were intended for. We always have a bit of a tension with this sort of legacy option because we want to keep them documented just enough to be useful to someone who finds an existing script/etc using them and wants to know what they do, but not to take up so much space that they might distract users from finding the modern alternative they should consider instead. As a compromise in that vein here I've created a new section about these options under the local backend documentation, which then gives us the space to go into some detail about the various behaviors and interactions and also to discuss their history and our recommended alternatives. I then simplified all of the other mentions of these in command documentation to just link to or refer to the local backend documentation. My hope then is that folks who need to know what these do can still find the docs, but that information can be kept out of the direct path of new users so they can focus on learning about remote backends instead. This is certainly not the most ideal thing ever, but it seemed like the best compromise between the competing priorities I described above.	5 years ago
Matthew Frahry	13b41d59f5	Website Test Fix	5 years ago
Matthew Frahry	3546650ac6	backend/azurerm: adding the right role name	5 years ago
Robin Norwood	31323b911b	Add callout to resource targeting tutorial	5 years ago
Matthew Frahry	a978d4ee99	website: adding the new fields to azurerm	5 years ago
Tej-Singh-Rana	2a49d908b8	fix the typo (#28140)	5 years ago
Pam Selle	683422e54f	Merge pull request #28113 from hashicorp/pselle/provider_sensitive_attrs_docs ... Update documentation for provider_sensitive_attrs experiment	5 years ago
James Bardin	c6278bbe37	Merge pull request #28042 from jasons42/update-workspaces-docs ... Indicate etcdv3 support for multiple workspaces in docs	5 years ago
Alisdair McDiarmid	b6ca782993	documentation: Clarify JSON diagnostic traversal ... The traversal value is normally a valid HCL string, but can be simplified if a traversal step has a complex index value (e.g. an object). This means it is not always parseable HCL, so this commit updates the documentation to clarify this and explicitly record that we do not guarantee its contents are stable. The purpose of these values is purely for building human-readable UI.	5 years ago
Alisdair McDiarmid	53739f0aac	Merge pull request #28108 from hashicorp/alisdair/validate-json-format-version ... cli: Add format version to validate -json output	5 years ago
Martin Atkins	89b2405080	lang/funcs: "sensitive" and "nonsensitive" functions ... These aim to allow hinting to Terraform about situations where it's not able to automatically infer value sensitivity. "nonsensitive" is for situations where Terraform's behavior is too conservative, such as when a new value is derived from a sensitive value in such a way that all of the sensitive content is removed. "sensitive", on the other hand, is for situations where Terraform can't otherwise infer that a value is sensitive. These situations should be pretty rare in a module that's making effective use of sensitive input variables and output values, but the documentation shows one example of an uncommon situation where a more direct hint via this function would be needed. Both of these functions are aimed at only occasional use in unusual situations. They are here for reasons of pragmatism, not because we expect them to be used routinely or recommend their use.	5 years ago
Paddy	0b5c4a6a2c	Accept TF_LOG=json to enable TRACE logs in JSON format ... This is not currently a supported interface, but we plan to release tool(s) that consume parts of it that are more dependable later, separately from Terraform CLI itself.	5 years ago
Pam Selle	81e8167a4c	Update documentation for provider_sensitive_attrs experiment ... Update documentation to reference that this experiment is now default in 0.15+	5 years ago
Alisdair McDiarmid	46a29b13ed	cli: Add format version to validate -json output ... In line with the other complex JSON output formats for plan and provider schema, here we add an explicit `format_version` field to the JSON output of terraform validate.	5 years ago
Alisdair McDiarmid	2a85f0483f	website: Update validate -json diags documentation ... Updated to include details about the new "snippet" object in JSON diagnostics.	5 years ago
Martin Atkins	dc7f2b7314	website: docs for the terraform validate JSON output	5 years ago
Jason Smith	024035114a	Fix broken link error ... Link to https://consul.io/ is not actually broken but returns a 307 redirect to https://www.consul.io/ which the broken link test counts as a failure.	5 years ago
Jason Smith	8663b2100a	Indicate etcdv3 support for multiple workspaces	5 years ago
Antoine Cotten	3442873cdb	docs: Update link to HCL native syntax spec	5 years ago
Masayuki Morita	31a5aa1878	command/init: Add a new flag `-lockfile=readonly` (#27630) ... Fixes #27506 Add a new flag `-lockfile=readonly` to `terraform init`. It would be useful to allow us to suppress dependency lockfile changes explicitly. The type of the `-lockfile` flag is string rather than bool, leaving room for future extensions to other behavior variants. The readonly mode suppresses lockfile changes, but should verify checksums against the information already recorded. It should conflict with the `-upgrade` flag. Note: In the original use-case described in #27506, I would like to suppress adding zh hashes, but a test code here suppresses adding h1 hashes because it's easy for testing. Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	5 years ago
Aaron Lane	f172585eaa	Fix Kitchen-Terraform language in test experiment ... This isn't incredibly important, but Kitchen-Terraform is written in and requires tests to be written in Ruby.	5 years ago
Kristin Laemmert	106bcd3bf0	update to match new default branch name (#27909)	5 years ago
Alisdair McDiarmid	79f855b83b	Merge pull request #27840 from OJFord/docs-27554 ... Document `inline` & `on_failure` behaviour	5 years ago
Rachel Sharp	3cb4918739	Merge pull request #27862 from hashicorp/add-state-learn-tutorial ... Add State Learn tutorial to State docs	5 years ago
James Bardin	c103242bef	Merge pull request #27885 from hashicorp/jbardin/show-json ... jsonstate: indicate schema version mismatch during encoding	5 years ago
James Bardin	c7995b7d4b	update show -json docs	5 years ago
Martin Atkins	8d37a70987	website: Initial docs for the module integration testing experiment ... Since this is still at an early phase and likely to change significantly in future iterations, rather than attempting to guess on a suitable final location for documenting the testing feature I've instead taken the unusual approach of adding a new page that is explicitly about the experiment. My expectation is that once we conclude the experiment we'll replace this new page with a stub that just explains that there was once an experiment and then links to whatever final feature unfolded from the research. The URL for this page is hard-coded into the warning message in the "terraform test" command, so as we continue to evolve this feature in future releases we'll need to update the callout note on the page about which Terraform CLI version it's currently talking about, so users of older versions can clearly see when they'd need to upgrade in order to participate in a later incarnation of the experiment.	5 years ago
Rachel Sharp	2f287b41de	Add State Learn tutorial to State docs	5 years ago
Oliver Ford	2f7c368d91	Document `inline` & `on_failure` behaviour ... cf. #27554	5 years ago
Pam Selle	8d2fbd4cd8	Remove deprecation on undeclared variable, docs, and summary adjustment (#27795) ... * Remove deprecation on undeclared variable Remove deprecation and add docs specific to the behavior around undeclared variable values * Limit full warnings to 2 instances, then summary This way, the third warning is a summary, rather than the fourth warning being the summary	5 years ago
James Bardin	d54a9b176b	Update website/docs/language/providers/configuration.html.md ... Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
James Bardin	e40727076f	Update website/docs/language/modules/develop/providers.html.md ... Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
James Bardin	9859d4e70b	Update website/docs/language/modules/develop/providers.html.md ... Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
James Bardin	dfd8424392	link configuration aliases between pages	5 years ago
James Bardin	1bb602859a	update docs for configuration_aliases ... Remove references to the "proxy configuration block" concept, and add examples showing the usage of `configuration_aliases`.	5 years ago
Stephen	e39abbf6f0	fix regex logical or documentation (#27637) ... * fix regex logical or documentation Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
Robin Norwood	181048b913	Add crosslink to new Learn tutorial	5 years ago
Alisdair McDiarmid	888f36aebb	cli: Remove positional plan argument from graph ... To make the command arguments easier to understand and extend, we are moving away from positional arguments. This commit changes the graph command to take a `-plan` flag instead of an optional trailing path.	5 years ago
Pam Selle	6da55c0521	Update grammar for flags	5 years ago
Andor Markus	f658531883	Updating terraform workspace website list.html.md new.html.md select.html.md files thus it reflect the current version of Terraform CLI	5 years ago
Pam Selle	e1b0e3ce92	Remove -module option for taint and untaint ... This has been an error with help text, and can be removed.	5 years ago
Alisdair McDiarmid	75d38b50b1	docs: Note: state pull upgrades to current version	5 years ago
Nick Fagerlund	6d016af7c5	website: Remove links to legacy provider docs for GitHub, ksyun ... These providers are now published to the registry, as planned.	5 years ago