157 Commits (4338b75acd20a64c39bdba8d9028e06175bbdde2)

Author	SHA1	Message	Date
Sahal Pathan	ea140f6dc8	Update version-constraints.mdx (#36565) ... Slight changes in docs: 1.1 => ~> 1.1	1 year ago
Christian Alexánder Polanco Valdez	a62fa224fc	Fix typo version-constraints.mdx ... I detected a typo while reading the page.	1 year ago
SimonVanEndern	8a5ffdbc09	Remove typo (duplicated "an") in references.mdx (#36309)	1 year ago
Naresh Reddy	43c089152a	Update conditionals.mdx (#36128) ... * Update conditionals.mdx * Update website/docs/language/expressions/conditionals.mdx Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com> * Update conditionals.mdx --------- Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com>	1 year ago
Corsin Ragettli	6aabaaabd3	fix(types.mdx): implement feedback ... Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com>	1 year ago
Corsin Ragettli	06191109e5	fix(types): add missing terraform/ infront of link	1 year ago
Corsin Ragettli	0ba91dc168	fix(types.mdx): reference the type-constraints page	1 year ago
Corsin Ragettli	5a619586d2	feat(types.mdx): add hint for difference of tuples and lists	1 year ago
nimzo6689	b4a634ced8	Remove Interpolation-only expressions from website/docs files (#36065) ... * Remove Interpolation-only expressions from website/docs files Interpolation-only expressions are deprecated in Terraform v0.12.14 See. https://github.com/terraform-linters/tflint-ruleset-terraform/blob/v0.10.0/docs/rules/terraform_deprecated_interpolation.md * Revert whitespace trimming at the end of lines * Preserve interpolation-only expressions for JSON * Preserve interpolation-only expressions for < 0.11 samples * Remove Interpolation-only expressions from website/docs files	1 year ago
trujillo-adam	8bdc1c8e3f	fixes #32423	1 year ago
Bruno Schaatsbergen	a8c9574d36	docs: apply feedback ... Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>	2 years ago
Bruno Schaatsbergen	6ada027d2c	docs: fix md formatting ... Signed-off-by: Bruno Schaatsbergen <git@bschaatsbergen.com>	2 years ago
Bruno Schaatsbergen	476b48bcd3	docs: clarify key quoting and formatting rules ... Signed-off-by: Bruno Schaatsbergen <git@bschaatsbergen.com>	2 years ago
Bruno Schaatsbergen	f5bb5e1cd2	chore: improve style ... Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com>	2 years ago
Bruno Schaatsbergen	42839e0dc3	docs: use a fully-qualified Developer path as a relative link ... Signed-off-by: Bruno Schaatsbergen <git@bschaatsbergen.com>	2 years ago
Bruno Schaatsbergen	05c6cf05d5	docs: add a note on `?` and `:`	2 years ago
trujillo-adam	732104c5a9	Merge pull request #35668 from hashicorp/docs/atru/reformat-terraform-block-ref ... CLI and lang updates assoc with tagging	2 years ago
James Nesta	bc6b1be4e2	Update version-constraints.mdx	2 years ago
James Nesta	bb2711af94	Update version-constraints.mdx	2 years ago
trujillo-adam	bf91b08ad3	update internal links to backend ref	2 years ago
Tu Nguyen	5c342b0d18	Update website/docs/language/expressions/types.mdx	2 years ago
Tu Nguyen	a3d362cf36	Update website/docs/language/expressions/types.mdx	2 years ago
Tu Nguyen	4c02938cee	Update website/docs/language/expressions/types.mdx ... Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>	2 years ago
Tu Nguyen	e681d36308	Update website/docs/language/expressions/types.mdx ... Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>	2 years ago
hedaya-khalif	22f64cbbcf	Fix #32601 ... Update Set data type description	2 years ago
Mathis Pierron	67d285b195	fix(docs): incorrect example ... The example given to illustrate the behaviour of logical operators is incorrect. `var.foo || var.foo.bar` would also produce an error if the operator was short-circuiting. The example should be with `var.foo && var.foo.bar`, that produces an error in terraform, but wouldn't if `||` could short-circuit	2 years ago
Radek Simko	8f7a9d1865	website: Enable highlighting for HCL snippets (#35354)	2 years ago
Martin Atkins	3b620bfe69	terraform: Stabilize the variable_validation_crossref experiment ... Previously we introduced a language experiment that would permit variable validation rules to refer to other objects declared in the same module as the variable. Now that experiment is concluded and its behavior is available for all modules. This final version deviates slightly from the experiment: we learned from the experimental implementation that we accidentally made the "validate" command able to validate constant-valued input variables in child modules despite the usual rule that input variables are unknown during validation, because the previous compromise bypassed the main expression evaluator and built its own evaluation context directly. Even though that behavior was not intended, it's a useful behavior that is protected by our compatibility promises and so this commit includes a slightly hacky emulation of that behavior, in eval_variable.go, that fetches the variable value in the same way the old implementation would have and then modifies the hcl evaluation context to include that value, while preserving anything else that our standard evaluation context builder put in there. That narrowly preserves the old behavior for expressions that compare the variable value directly to a constant, while treating all other references (which were previously totally invalid) in the standard way. This quirk was already covered by the existing test TestContext2Validate_variableCustomValidationsFail, which fails if the special workaround is removed.	2 years ago
Rose	0eac58dcab	Change the header names	2 years ago
Brian McClain	670bcb0cb1	root_block_device requires an index	2 years ago
Ari Summer	d12984064a	Correct EC2 instance encryption condition example in custom-conditions.mdx	2 years ago
Craig Wright	e539f46e85	Merge pull request #33581 from hongshaoyang/patch-1	3 years ago
hongshaoyang	171b9d7b70	Apply suggestions from code review ... Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>	3 years ago
James Bardin	771684058e	types documentation	3 years ago
Craig Wright	35baa30f36	Merge pull request #33132 from briskt/schparky-edit-types	3 years ago
briskt	88146627a3	PR feedback: edit phrase to avoid passive voice ... Co-authored-by: Judith Malnick <judith@hashicorp.com>	3 years ago
hongshaoyang	5b640a1b7c	Update version-constraints.mdx	3 years ago
hongshaoyang	dd7ea46c2a	Update version-constraints.mdx	3 years ago
Craig Wright	7d1e918a38	Merge pull request #32074 from bendrucker/patch-1	3 years ago
Chris Trombley	6d817660eb	docs: dissociate CV from preconditions and postconditions	3 years ago
Kieran Lowe	0a2f62c8a0	fix: update broken links to `checks` section in docs (#33357) ... This also capitalises the 'a' in assertions to keep it consistent with the rest of the document	3 years ago
Rose M Koron	46e47e07d9	Adding links to the Checks tutorial and fixing headers to be sentence case (#33328)	3 years ago
Liam Cervante	6fa5784129	Add documentation page for checks and assertions (#33241) ... * Add documentation page for checks and assertions * address comments * Apply suggestions from code review Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com> * address comments * Apply suggestions from code review Co-authored-by: Radek Simko <radek.simko@gmail.com> Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com> * address comments * Apply suggestions from code review Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com> * revamp choosing checks or other custom conditions section * expand on depends_on * fix issues link * Apply suggestions from code review Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com> * address comments * Apply suggestions from code review Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com> --------- Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com> Co-authored-by: Radek Simko <radek.simko@gmail.com>	3 years ago
Martin Atkins	b56af3a36a	website: Clarify what the "any" type constraint placeholder is for ... From helping folks in community forums I've noticed that many people misunderstand "type = any" as being a shorthand to avoid writing out a proper type constraint, rather than as a way to handle the very rare case where a module truly does not care what type of value it's accepting. This is understandable because the previous documentation only described how this feature behaved, and not what this feature was for. This new content instead leads by describing the single rare situation where this feature is appropriate to use, and only then explains some details of how it works. Hopefully this will help avoid misleading people into using this placeholder in inappropriate situations, and thus allow Terraform to give them better feedback about errors elsewhere in their configurations.	3 years ago
Schparky	786993cc72	reference parent type for consistency	3 years ago
Schparky	c1d350ef9b	add 'set' to the type list and clarify collection type hierarchy	3 years ago
Ashlee Boyer	32f7b8ebd0	Migrating links to new format	3 years ago
Laura Pacilio	1ce0b91e67	Merge pull request #32020 from hashicorp/fix-future-lang-2 ... Remove future-facing language from docs (WIP)	3 years ago
Brandon Croft	be5984d664	Merge pull request #32004 from hashicorp/brandonc/nested_attr_sensitive ... fix: don't reveal nested attributes with sensitive schema	4 years ago
Laura Pacilio	fbfe5b5a87	Merge pull request #31508 from wzyboy/docs/unknwon-value ... docs: fix typo regarding unknown values	4 years ago