13 Commits (83538fdd6bd4cdfd6435f2e97e1d438e736c9750)

Author	SHA1	Message	Date
drewmullen	e3b6c6403c	include sha example and git docs	5 years ago
Laura Pacilio	31af9adc00	Make all sentences start with caps + additional tweak wording edits	5 years ago
Laura Pacilio	d59777c12f	Update website/docs/language/modules/sources.html.md ... Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Laura Pacilio	277fe647b9	Remove back ticks from source module page	5 years ago
Laura Pacilio	a780f625e9	Fix metadata description format on all pages	5 years ago
Laura Pacilio	bc9065334e	Update description metadata per PR feedback	5 years ago
Laura Pacilio	e348477c79	Add description metadata to module sources	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	4e74a7a4f1	initwd: Error message for local paths escaping module packages ... Our module installer has a somewhat-informal idea of a "module package", which is some external thing we can go fetch in order to add one or more modules to the current configuration. Our documentation doesn't talk much about it because most users seem to have found the distinction between external and local modules pretty intuitive without us throwing a lot of funny terminology at them, but there are some situations where the distinction between a module and a module package are material to the end-user. One such situation is when using an absolute rather than relative filesystem path: we treat that as an external package in order to make the resulting working directory theoretically "portable" (although users can do various other things to defeat that), and so Terraform will copy the directory into .terraform/modules in the same way as it would download and extract a remote archive package or clone a git repository. A consequence of this, though, is that any relative paths called from inside a module loaded from an absolute path will fail if they try to traverse upward into the parent directory, because at runtime we're actually running from a copy of the directory that's been taking out of its original context. A similar sort of situation can occur in a truly remote module package if the author accidentally writes a "../" source path that traverses up out of the package root, and so this commit introduces a special error message for both situations that tries to be a bit clearer about there being a package boundary and use that to explain why installation failed. We would ideally have made escaping local references like that illegal in the first place, but sadly we did not and so when we rebuilt the module installer for Terraform v0.12 we ended up keeping the previous behavior of just trying it and letting it succeed if there happened to somehow be a matching directory at the given path, in order to remain compatible with situations that had worked by coincidence rather than intention. For that same reason, I've implemented this as a replacement error message we will return only if local module installation was going to fail anyway, and thus it only modifies the error message for some existing error situations rather than introducing new error situations. This also includes some light updates to the documentation to say a little more about how Terraform treats absolute paths, though aiming not to get too much into the weeds about module packages since it's something that most users can get away with never knowing.	5 years ago
Roger Berlind	b6885923d0	website: Add link to Modules in Package Sub-directories (#27980) ... * Add link to Modules in Package Sub-directories Add link to "Modules in Package Sub-directories" section at top of page * Fix broken links * Update aws link, fixes missing anchor linkcheck Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Nick Fagerlund	d1e8537b33	website: CLI: Update links to moved docs pages	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