81 Commits (c73a5fc07da195af2ee2b2958a04e495df00a7b1)

Author	SHA1	Message	Date
PenelopeFudd	247faca59d	website: formatdate function in the navigation sidebar	7 years ago
Nick Fagerlund	13166df619	website: move docs/index.html to docs/cli-index.html ... Terraform is way bigger than the core CLI tools and the language now, and the docs have grown accordingly. So we're adding a global index page to help users get around the many sections of the docs site, and bumping the CLI/core docs down so they're no longer at the top of the hierarchy. The "right" (as in, conceptually pure) way to do this would be to actually create a new level of directory hierarchy in between. But that would be real expensive and annoying — the amount of 301s and links to edit would be monumental, and it wouldn't gain us much beyond a certain picture-straightening satisfaction, so I'm resisting the temptation.	7 years ago
Nick Fagerlund	094a5d65d3	website: Use a middleman partial for "other docs" list instead of hardcoding it ... This relies on a commit in the terraform-website repo, and should make updating that list much less annoying.	7 years ago
David Chwalisz	ddb7e0ab20	fix `Publishing Modules` link of website documentation. ... Currently links to [Creating Modules](https://www.terraform.io/docs/modules/create.html) page. Should link to [Publishing Modules](https://www.terraform.io/docs/modules/publish.html) page. fixes #20636	7 years ago
Martin Atkins	9336c7fba3	website: Revamped module-authoring docs for Terraform v0.12 ... As well as some general consolidation and reorganizing, this also includes some updated advice for making the best use of new Terraform v0.12 features to create infrastructure building-blocks. In particular, the "Module Usage" documentation is now consolidated into the configuration section in order to bring all of our general language documentation together, and the top-level "Modules" section is now primarily focused on module _authors_ as an audience, covering topics such as publishing modules and designing them for reuse.	7 years ago
Kristin Laemmert	5ebf8b2992	website: fix link (#20501)	7 years ago
Kristin Laemmert	f44e4b2c6a	website: add documentation for terraform providers schema (#20468) ... * website: add documentation for terraform providers schema	7 years ago
James Bardin	eada955721	Merge pull request #19070 from mars/postgres-backend ... Postgres backend	7 years ago
Martin Atkins	f4bc502f51	website: Documentation for "terraform 0.12upgrade"	7 years ago
Mars Hall	312d408f06	📚 pg backend docs	7 years ago
Nick Fagerlund	01eb224469	website: Large, on-brand link preview image for marketing pages (/intro/*) ... Although /intro/getting-started includes docs content, those pages currently redirect to the Learn platform, and so shouldn't be affected by the large unfurl image.	7 years ago
Nick Fagerlund	0a58004da4	website: Add JSON output format to nav sidebar	7 years ago
Nick Fagerlund	d1daa7e518	website: Make 0.11 and 0.12 subsections of 'Configuration Language'	7 years ago
Nick Fagerlund	a9bcc0fe06	website: Fix sidebar nav links and 'sidebar_current' IDs for 0.11 docs ... Because of the different possibilities for arranging the nav sidebars, we want to make sure: - IDs for the 0.11 and 0.12 language docs have a common prefix. - That prefix is not the exact string `docs-config`. Have I mentioned before that I really dislike this prefix matching behavior.	7 years ago
Nick Fagerlund	11cfdf3b67	website: Add 0.11 configuration language docs (WIP) ... This is a non-working commit, because a bunch of links (including the sidebar nav) are broken. Using a transition commit like this makes it easier to see the changes necessary to get this content woven into the site.	7 years ago
Nick Fagerlund	0fddabf972	website: Reorganize nav sidebars to improve jumps between sections	7 years ago
Martin Atkins	954d38e870	lang: New file-hashing functions ... In prior versions, we recommended using hash functions in conjunction with the file function as an idiom for detecting changes to upstream blobs without fetching and comparing the whole blob. That approach relied on us being able to return raw binary data from file(...). Since Terraform strings pass through intermediate representations that are not binary-safe (e.g. the JSON state), there was a risk of string corruption in prior versions which we have avoided for 0.12 by requiring that file(...) be used only with UTF-8 text files. The specific case of returning a string and immediately passing it into another function was not actually subject to that corruption risk, since the HIL interpreter would just pass the string through verbatim, but this is still now forbidden as a result of the stricter handling of file(...). To avoid breaking these use-cases, here we introduce variants of the hash functions a with "file" prefix that take a filename for a disk file to hash rather than hashing the given string directly. The configuration upgrade tool also now includes a rule to detect the documented idiom and rewrite it into a single function call for one of these new functions. This does cause a bit of function sprawl, but that seems preferable to introducing more complex rules for when file(...) can and cannot read binary files, making the behavior of these various functions easier to understand in isolation.	7 years ago
Martin Atkins	2f8f7d6f4d	lang/funcs: Type conversion functions ... It's not normally necessary to make explicit type conversions in Terraform because the language implicitly converts as necessary, but explicit conversions are useful in a few specialized cases: - When defining output values for a reusable module, it may be desirable to force a "cleaner" output type than would naturally arise from a computation, such as forcing a string containing digits into a number. - Our 0.12upgrade mechanism will use some of these to replace use of the undocumented, hidden type conversion functions in HIL, and force particular type interpretations in some tricky cases. - We've found that type conversion functions can be useful as _temporary_ workarounds for bugs in Terraform and in providers where implicit type conversion isn't working correctly or a type constraint isn't specified precisely enough for the automatic conversion behavior. These all follow the same convention of being named "to" followed by a short type name. Since we've had a long-standing convention of running all the words together in lowercase in function names, we stick to that here even though some of these names are quite strange, because these should be rarely-used functions anyway.	7 years ago
Martin Atkins	da51e72cbb	lang/functions: set functions from cty ... The sethaselement, setintersection, and setunion functions are defined in the cty stdlib. Making them available in Terraform will make it easier to work with sets, and complement the currently-Terraform-specific setproduct function. In the long run setproduct should probably move into the cty stdlib too, but since it was submitted as a Terraform function originally we'll leave it here now for simplicity's sake and reorganize later.	7 years ago
Martin Atkins	edb5f82de1	lang/funcs: Convert the "setproduct" function to the new approach ... In our new world it produces either a set of a tuple type or a list of a tuple type, depending on the given argument types. The resulting collection's element tuple type is decided by the element types of the given collections, allowing type information to propagate even if unknown values are present.	7 years ago
Nick Fagerlund	ac45e43fda	website: Finish moving "writing custom providers" to /docs/extend/ ... This document was previously copied to the "Extending Terraform" section (in the terraform-website repo), and the old URL was redirected so that the copy in /guides can no longer be reached on the website. But the old copy of the file remained, and now it runs the risk of confusing contributors, since the copy in terraform-website/.../docs/extend is the more up-to-date version.	7 years ago
Martin Atkins	c753df6a93	lang/funcs: templatefile function ... This function is similar to the template_file data source offered by the template provider, but having it built in to the language makes it more convenient to use, allowing templates to be rendered from files anywhere an inline template would normally be allowed: user_data = templatefile("${path.module}/userdata.tmpl", { hostname = format("petserver%02d", count.index) }) Unlike the template_file data source, this function allows values of any type in its variables map, passing them through verbatim to the template. Its tighter integration with Terraform also allows it to return better error messages with source location information from the template itself. The template_file data source was originally created to work around the fact that HIL didn't have any support for map values at the time, and even once map support was added it wasn't very usable. With HCL2 expressions, there's little reason left to use a data source to render a template; the only remaining reason left to use template_file is to render a template that is constructed dynamically during the Terraform run, which is a very rare need.	7 years ago
Nick Fagerlund	d2abdc23ac	website: Structural edit of configuration language docs ... This commit is a wide-ranging set of edits to the pages under /docs/configuration. Among other things, it - Separates style conventions out into their own page. - Separates type constraints and conversion info into their own page. - Conflates similar complex types a little more freely, since the distinction is only relevant when restricting inputs for a reusable module or resource. - Clarifies several concepts that confused me during edits.	7 years ago
Nick Fagerlund	ab88f8ca0f	website: Update and link the page about remote backend operations (#19203)	8 years ago
Radek Simko	edaa4bbc82	lang: Add fileexists function	8 years ago
Martin Atkins	0b710792a8	website: "functions" layout "Terraform Language" is back ... In the heirarchy, both "Terraform Language" and "Functions" are "up" from the individual function reference pages, so we'll class them as such to use the back-facing arrow instead of the forward-facing arrow.	8 years ago
Martin Atkins	1360948a41	website: document the functions "keys", "lookup", and "values" ... I missed these on the first pass because in the legacy function table they are, for some reason, added in a different place than the others.	8 years ago
Martin Atkins	a35c0f3cbf	website: Docs for all of the "filesystem" functions	8 years ago
Martin Atkins	c8da3e568f	website: Add remaining functions to the functions section sidebar ... These links don't lead anywhere yet.	8 years ago
Martin Atkins	48d940323e	website: Beginnings of "Functions" configuration section ... Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.	8 years ago
Martin Atkins	e5e3452ffa	website: Reorganize the "Configuration" docs section ... With the additional configuration language features coming in Terraform v0.12, our existing documentation structure is beginning to strain. Here we reorganize the navigation slightly in order to introduce the concepts in a more appropriate order so that we can reveal complexity more gradually. Subsequent commits will revise the content of these pages to better reflect the new sequencing. The "Environment Variables" page is moved from the Configuration section into the "Commands" section, since it is not considered a part of the configuration language and thus more appropriate in the CLI documentation. The old placement is reflective of the broader purpose that the "Configuration" section had originally, but its new focus will be on the Terraform language (.tf files) in particular, with other aspects of customizing Terraforms behavior covered in other sections.	8 years ago
Luke Kysow	3eafbf3861	Add link to Terraform's GitHub Actions docs (#19091)	8 years ago
Paul Hinze	6cdc464341	Initial draft of Core Workflow Guide	8 years ago
Sander van Harmelen	7fb2d1b8de	Implement the Enterprise enhanced remote backend	8 years ago
kfishner	6deec5d7bf	add 0.12 guide	8 years ago
Walter Dolce	b60501290c	Make "v3" in etcd visible in the backend types sidebar	8 years ago
Clint	76974209ec	Update guides.erb ... Update "Writing Custom Providers" guide link to new Extend section	8 years ago
Brian Flad	9b295e2bc7	docs/internal: Fix sidebar navigation for Remote Service Discovery page	8 years ago
Nick Fagerlund	66ff8f8bed	website: Deprecation notes about "terraform push" ... Also: - In the getting started guide, the TFE content was all tailored to the older run-locally workflow. I've replaced it with some brief explanation and a link to the dedicated TFE getting started guide. - Fixed a sidebar link glitch in the configuration section. (Both "Terraform" and "Terraform Enterprise" were marked as active if you were on the TFE page.) - Renamed the "Terraform Enterprise" page "Terraform Push." (Some people have gotten confused and landed on this page when trying to set up the `atlas` remote backend.)	8 years ago
James Bardin	5458ea9aff	update etcd documentation links ... Add missing link to ectdv3. Update etcd v2 link to the current v2 README, which highlights the pending deprecation.	8 years ago
Chris Griggs	18975d7270	website: present provider documentation via categories ... We have outgrown the single flat list presentation of providers due to the shear number now present, so we'll move here to a model where the providers are split into a number of categories that each contain a smaller list. The full list is still included in the body of the main index page for quick access via search, but the categories make for a more accessible navbar for those who are just browsing.	8 years ago
Clint	f43d66e143	Revert "Restructure terraform.io to include provider categories (#16934)" (#16966) ... This reverts commit 7481c113ee.	8 years ago
Chris Griggs	7481c113ee	Restructure terraform.io to include provider categories (#16934) ... * add catagory files * try new source path * cleaning up formatting * fixin * add all providers to providers index page * add descriptions * add link to form and first two providers * small edits * small edits * small changes * add community providers and decription edit from marketing * add some lines to improve design * fix typos	8 years ago
Chris Marchesi	c2c9e4f418	Merge pull request #16583 from hashicorp/azurerm-website ... Renaming the Azure Provider	8 years ago
Maciej Skierkowski	c1469aa39e	Rename links for TFE classic and beta	8 years ago
Maciej Skierkowski	8c2ed71163	Updates guides menu to use new TFE paths	8 years ago
clint shryock	ccbd3db2b7	add opentelekomcloud link to docs	8 years ago
Nolan Davidson	a50a383946	Additional work on the habitat provisioner. ... Signed-off-by: Nolan Davidson <ndavidson@chef.io>	8 years ago
Chris Griggs	9d863fee62	website: Add the Null provider to the list of providers	9 years ago
Martin Atkins	116003f157	website: downloads nav link to 0.11 upgrade guide	9 years ago