terraform

Commit Graph

Author	SHA1	Message	Date
Kevin Wang	03e262a70b	chore: rewrite internal redirects (#32038 )	3 years ago
Matthew Garrell	03bff99caa	Merge pull request #31954 from hashicorp/mg_no_code_prov_followup Adding mention of no-code to Creating Modules section of TF Language docs	3 years ago
Matthew Garrell	a50d8cfc11	Adding mention of no-code to Modules section of TF Language docs	3 years ago
Bryce Kalow	b54017ef83	website: content updates for developer (#31779 ) Co-authored-by: Matthew Garrell <69917312+mgarrell777@users.noreply.github.com> Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com> Co-authored-by: Kevin Wang <kwangsan@gmail.com> Co-authored-by: Judith Malnick <judith@hashicorp.com> Co-authored-by: Martin Atkins <mart@degeneration.co.uk> Co-authored-by: HashiBot <62622282+hashibot-web@users.noreply.github.com>	4 years ago
kmoe	56a1e0d1c6	allow cross-package move statements (#31556 )	4 years ago
Gerard Nguyen	fd21e6e510	Update website/docs/language/modules/develop/providers.mdx Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>	4 years ago
Gerard Nguyen	d521d379f8	Add link to default provider configuration definition	4 years ago
Laura Pacilio	eea860e0cf	Fixing typos and doing a read through	4 years ago
Laura Pacilio	04d329a9e1	Add references to custom conditions on related pages	4 years ago
Kyle Davies	0ea6874bc1	Change aws.dest to aws.dst Documentation is wrong the `configuration_aliases` should be `[ aws.src, aws.dst ]` not `[ aws.src, aws.dest ]`.	4 years ago
Drew Hodun	a26b551d47	added github.com commit reference example	4 years ago
Laura Pacilio	9e28fc44cd	Merge branch 'main' into fix-remote-backend-references	4 years ago
Martin Atkins	74761b2f8b	getmodules: Use go-getter v1.5.10 and return to upstream GitGetter There was an unintended regression in go-getter v1.5.9's GitGetter which caused us to temporarily fork that particular getter into Terraform to expedite a fix. However, upstream v1.5.10 now includes a functionally-equivalent fix and so we can heal that fork by upgrading. We'd also neglected to update the Module Sources docs when upgrading to go-getter v1.5.9 originally and so we were missing documentation about the new "depth" argument to enable shadow cloning, which I've added retroactively here along with documenting its restriction of only supporting named refs. This new go-getter release also introduces a new credentials-passing method for the Google Cloud Storage getter, and so we must incorporate that into the Terraform-level documentation about module sources.	4 years ago
Laura Pacilio	f55af42086	Update module sources page	4 years ago
Dylan Staley	21cbb5b392	migrate docs to mdx	4 years ago
Patrick Decat	6530055d18	website: Refactoring "Renaming a Module Call" should include a moved block	4 years ago
Laura Pacilio	529a2c34df	Update note and add learn call out	4 years ago
Dylan Staley	0e48f58688	Revert "migrate docs to mdx" This reverts commit `3cb12b5a52`.	4 years ago
Dylan Staley	3cb12b5a52	migrate docs to mdx	4 years ago
Martin Atkins	14a8668486	website: "Refactoring" documentation firmer advice about removing moved blocks Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>	4 years ago
Martin Atkins	86e5aacacd	website: Documentation about "moved" blocks This is documentation for the first set of refactoring-related features, all based on the new "moved" blocks in the Terraform language. I've named the documentation section "refactoring" because in previous discussions with users that seems to be the term they use to describe the underlying need. "moved" blocks are our first language feature intended to meet that need, although it probably won't be the last as we consider other requirements in later releases. My intent here is that once we've published this it should eventually end up being the first result for a web search for the topic of Terraform refactoring.	4 years ago
Melissa Gurney Greene	0062e7112a	Update publish.html.md (#29671 ) Updated language around contributing modules with overlapping features in the Publishing Modules section: "We welcome..." (all contributions)	5 years ago
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	2718d2addc	Add description metadata to module block page	5 years ago
Laura Pacilio	3baddbef0e	Add description metadata to creating modules pagey	5 years ago
Laura Pacilio	e348477c79	Add description metadata to module sources	5 years ago
Laura Pacilio	4044fe30d3	Add description metadata to modules overview 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	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
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
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
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
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

44 Commits (4835deddaef450198bba00a50311f2ada6f79b96)