terraform

Commit Graph

Author	SHA1	Message	Date
James Bardin	8b53637230	Update website/docs/language/values/variables.html.md Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>	5 years ago
James Bardin	4f88445d05	Update website/docs/language/values/variables.html.md Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>	5 years ago
James Bardin	2195d7a45f	Update website/docs/language/values/variables.html.md Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>	5 years ago
James Bardin	46bbe66cd0	Update website/docs/language/values/variables.html.md Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>	5 years ago
James Bardin	03ed766454	nullable doc update	5 years ago
James Bardin	6a1afd2dc3	nullable variable docs Add `nullable` to the variable documentation. Remove "module" from the "null means omission" part of the null type documentation.	5 years ago
Radek Simko	7a95bbf019	docs: Add note about multiple variable validation blocks (#29299 )	5 years ago
Laura Pacilio	a780f625e9	Fix metadata description format on all pages	5 years ago
Laura Pacilio	603e156bb9	Update input variables page metadata	5 years ago
Laura Pacilio	14d6e0dea9	Add Terraform key work to description metadata	5 years ago
Laura Pacilio	07accd7a38	Add page metadata to variables and outputs overview	5 years ago
Laura Pacilio	bca3957e17	Update description metadata for input variables	5 years ago
Martin Atkins	a945b379d8	website: Explicit examples of -var escaping in various shells The -var command line option comes with the disadvantage that a user must contend both with Terraform's own parser and with the parser in whichever shell they've decided to use, and different shells on different platforms have different rules. Previously we've largely just assumed that folks know the appropriate syntax for the shell they chose, but it seems that command lines involving spaces and other special characters arise rarely enough in other commands that Terraform is often the first time someone needs to learn the appropriate syntax for their shell. We can't possibly capture all of the details of all shells in our docs, because that's far outside of our own scope, but hopefully this new section will go some way to give some real examples that will help folks figure out how to write suitable escape sequences, if they choose to set complex variable values on the command line rather than in .tfvars as we recommend elsewhere on this page.	5 years ago
Judith Malnick	044c439dbc	Gloss of top docs pages (#28891 ) * clarify input variables opening sentence * adjust variables description * claraify providers text and add learn callout * add description to providers page * add desscription and clarify provider configuration * add deprecation note to versions in proivder configs * add hands on callout and clarify next steps in intro * link to language collection from language docs * give more context about configurtion language up front * clarify output top page * reorganize for each intro to present feature before notes * move description before link out and remove passive voice * fix typo * clarify purpose of plan * move explanation before learn link and fully spell boolean * add a syntax heading to separate intro from details * add learn callout to module source docs * clean up intro to provider requirements and add link * Apply suggestions from code review Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
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
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
Nick Fagerlund	7a8dd326c6	website: Language: Update links to moved pages	5 years ago
Nick Fagerlund	78dcc8dc1b	website: Language: Move files to match new URL structure	5 years ago

18 Commits (27aa51687ea5d271b2fa68ea61bc52b7cfb09dd5)