5795 Commits (paddy_module_attribution_tmp)

Author	SHA1	Message	Date
Paddy Carver	f461614ebc	Add documentation for provider_meta.	6 years ago
Martin Atkins	ff4ea042c2	config: Allow module authors to specify validation rules for variables ... The existing "type" argument allows specifying a type constraint that allows for some basic validation, but often there are more constraints on a variable value than just its type. This new feature (requiring an experiment opt-in for now, while we refine it) allows specifying arbitrary validation rules for any variable which can then cause custom error messages to be returned when a caller provides an inappropriate value. variable "example" { validation { condition = var.example != "nope" error_message = "Example value must not be \"nope\"." } } The core parts of this are designed to do as little new work as possible when no validations are specified, and thus the main new checking codepath here can therefore only run when the experiment is enabled in order to permit having validations.	6 years ago
Martin Atkins	02576988c1	lang: "try" and "can" functions ... These are intended to make it easier to work with arbitrary data structures whose shape might not be known statically, such as the result of jsondecode(...) or yamldecode(...) of data from a separate system. For example, in an object value which has attributes that may or may not be set we can concisely provide a fallback value to use when the attribute isn't set: try(local.example.foo, "fallback-foo") Using a "try to evaluate" model rather than explicit testing fits better with the usual programming model of the Terraform language where values are normally automatically converted to the necessary type where possible: the given expression is subject to all of the same normal type conversions, which avoids inadvertently creating a more restrictive evaluation model as might happen if this were handled using checks like a hypothetical isobject(...) function, etc.	6 years ago
Pam Selle	cd6c93774a	Update docs to reflect current behavior	6 years ago
Martin Atkins	2a95d98383	docs: terraform state show is not machine-readable ... In earlier versions of Terraform the result of terraform state show was in the pre-0.12 "flatmap" structure that was unable to reflect nested data structures. That was fixed in Terraform 0.12, but as a consequence this statement about the output being machine-parseable (which was debateable even in older versions) is incorrect. Fortunately, we now have "terraform show -json" to get output that is intentionally machine-parseable, so we'll recommend to use that instead here. The JSON output of that command is a superset of what's produced by "terraform state show", so should be usable to meet any use-case that might previously have been met by parsing the "terraform state show" output.	6 years ago
Pam Selle	948d4d0ecf	Merge pull request #23749 from jasonwalsh/master ... website: update publishing modules documentation	6 years ago
Pam Selle	4977120764	Merge pull request #23733 from GennadySpb/patch-1 ... Change Yandex.Cloud provider name in index	6 years ago
jasonwalsh	62aae82913	website: update publishing modules documentation	6 years ago
Nick Fagerlund	413e423bba	website: Use canonical URLs for learn.hashicorp.com links ... The .html suffix redirects correctly, but it's not the 'real' path and thus can throw off analytics.	6 years ago
GennadySpb	e4c4c8cab5	Change Yandex.Cloud provider name in index ... 'Yandex' -> 'Yandex.Cloud'	6 years ago
Nick Fagerlund	c0176aeab3	website: Revise sensitive data in state page	6 years ago
Pam Selle	76831793d0	Merge pull request #23265 from lucazz/update_docs_for_outputs ... Update Output values docs	6 years ago
Pam Selle	3bcea18d1c	Update outputs.html.md	6 years ago
Pam Selle	31b56207e0	Update outputs.html.md	6 years ago
Pam Selle	a93298bd14	Merge pull request #23656 from hashicorp/paddy_gcs_backend_env_var ... Add a backend-specific env var for the GCS backend.	6 years ago
Igor Vodka	be89975667	Fix markdown being misused in docs	6 years ago
Pam Selle	5db7afa545	Merge pull request #23645 from patryk/patch-1 ... Cloudflare, not CloudFlare	6 years ago
Paddy Carver	b8752c7610	Add a backend-specific env var for the GCS backend. ... Right now, the only environment variable available is the same environment variable that will be picked up by the GCP provider. Users would like to be able to store state in separate projects or accounts or otherwise authenticate to the provider with a service account that doesn't have access to the state. This seems like a reasonable enough practice to me, and the solution seems straightforward--offer an environment variable that doesn't mean anything to the provider to configure the backend credentials. I've added GOOGLE_BACKEND_CREDENTIALS to manage just the backend credentials, and documented it appropriately.	6 years ago
Martin Atkins	bfbd00a23c	website: Note about using jsonencode/yamlencode in templatefile ... It's a common source of errors to try to produce JSON or YAML syntax using string concatenation via our template language but to miss some details like correct string escaping, quoting, required commas, etc. The jsonencode and yamlencode functions are a better way to generate JSON and YAML, but it's not immediately obvious that both of these functions are available for use in external templates (via templatefile) too. Given that questions related to this come up a lot in our community forum and elsewhere, it seems worth having a documentation section to show the pattern of having a template that consists only of a single function call.	6 years ago
Patryk Szczygłowski	03739a99ff	Cloudflare, not CloudFlare	6 years ago
Martin Atkins	c06675c616	command: New -compact-warnings option ... When warnings appear in isolation (not accompanied by an error) it's reasonable to want to defer resolving them for a while because they are not actually blocking immediate work. However, our warning messages tend to be long by default in order to include all of the necessary context to understand the implications of the warning, and that can make them overwhelming when combined with other output. As a compromise, this adds a new CLI option -compact-warnings which is supported for all the main operation commands and which uses a more compact format to print out warnings as long as they aren't also accompanied by errors. The default remains unchanged except that the threshold for consolidating warning messages is reduced to one so that we'll now only show one of each distinct warning summary. Full warning messages are always shown if there's at least one error included in the diagnostic set too, because in that case the warning message could contain additional context to help understand the error.	6 years ago
cgriggs01	c355fbd67c	add stackpath links	6 years ago
Kyle MacDonald	26131d948c	website: add yt video to /intro	6 years ago
cgriggs01	650250c471	move provider link page	6 years ago
Graham Davison	e32641c9ce	website/docs: Corrects function name in `cidrsubnets` function documentation (#23473)	6 years ago
cgriggs01	1c9ed3927a	add commmunity providers	6 years ago
Chris Griggs	7ef92417d1	Merge pull request #23456 from hashicorp/cgriggs01-opennebula ... [Website] OpenNebula provider links	6 years ago
Jon Schulman	722eae2cec	website: Fix example reference for remote backend (#23455) ... Example reference had a missing `=` sign on line 133; this causes the workspace reference not to parse properly	6 years ago
Martin Atkins	7cf782c1bf	states/statefile: Better error messages for some unsupported v3 cases ... There are a few situations that we've seen arise quite commonly for folks upgrading from Terraform 0.11 to 0.12. These particular problems are not things that Terraform 0.12 can fix automatically during upgrading, but we can at least give some better feedback to users that they ought to be addressed _before_ upgrading. The provider address problem is already detected and flagged by the "terraform 0.11checklist" command that folks should run as part of their upgrade process, but the module address problem is not something we noticed was lacking validation in 0.11 and so the checklist tool doesn't cover it. Due to the lack of coverage in the checklist tool, this commit also includes an additional section in the upgrade guide that mentions the problem and gives instructions on how to address it.	6 years ago
cgriggs01	b82a266f40	add opennebula links	6 years ago
Nick Fagerlund	6af552bea6	website: interpolation: clean up more placeholder formatting	6 years ago
Carlos Vega Meyer	fa22084e3a	website: interpolation.html.md: "module" is literal ... `MODULE` should be lowercase since it's not a placeholder for the actual module name.	6 years ago
George Christou	91100c003c	lang/funcs: Add more `trim*` functions (#23016) ... * lang/funcs: Add `trim*` functions	6 years ago
cgriggs01	5188f5d5c4	add huawei links	6 years ago
Martin Atkins	2423f266fb	website: example of "terraform taint" with a grandchild module ... I've seen folks ask about how to express this in resource address syntax a number of times now, so adding this example here to illustrate how it looks when there are multiple levels of module to traverse through. This is redundant with other information further up the page, but having it as an entirely separate example gives an opportunity to include more introductory text to explain what the example is showing.	6 years ago
cgriggs01	ebb0ca2d23	[Website] Provider links	6 years ago
cgriggs01	4a46d0c212	[Website] vThunder links	6 years ago
Yuki Ito	72c910cebc	website: Fix typographical errors in the docs for base64sha256/512	6 years ago
andrewjkeith	6cb9aaacfe	website: Fix extension_requests argument name for Puppet provisioner	6 years ago
Paddy	ba7679b679	website: Remove reference to the now-deprecated pgp_key provider design pattern	6 years ago
Roger Berlind	de4ef9c546	website: Clarify workspace concepts for remote backend ... There are some differences between the Terraform CLI and Terraform Cloud ideas of workspaces. This documentation aims to explain those differences and show different patterns for configuring the remote backend and the implications of different approaches.	6 years ago
James Bardin	cf49f794d7	Merge pull request #22821 from xiaozhu36/master ... backend(oss): add a new field ecs_role_name to support more scenario	6 years ago
cgriggs01	a5ad6dd57b	update CDA and Okta	6 years ago
Lucas do Amaral Saboya	806397803c	Update Output values docs.	6 years ago
He Guimin	bfae627112	add a new field ecs_role_name to support more scenario	6 years ago
Pam Selle	f9f7320438	Merge pull request #17911 from vkatsikaros/patch-2 ... Expand example explanation	6 years ago
Pam Selle	4f1d363b98	Change wording back to attach, add for_each mention	6 years ago
vkatsikaros	22321efa71	Expand example explanation ... As mentioned in #17871 the current example can hide the fact that the module path plays an important role. The example's explanation is expanded. Moreover, the verb "attach" is replaced with "map" to make the vocabulary consistent with the wording in the documentation of the terraform state.	6 years ago
Pam Selle	5070ab7989	Merge pull request #23185 from scott1138/patch-1 ... Update taint docs - for_each	6 years ago
cgriggs01	e3b18cd0d9	[Website] CherryServer doc links	6 years ago