298 Commits (799b49d7c81dff1a92ff03c1955d1d389026b0c6)

Author	SHA1	Message	Date
Martin Atkins	e405b58c79	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
Kristin Laemmert	94f29f2c44	port cidr functions	8 years ago
Kristin Laemmert	97f158a497	porting functions	8 years ago
Kristin Laemmert	05e3f9af8d	porting crypto functions	8 years ago
Kristin Laemmert	7393a40586	porting encoding functions	8 years ago
Martin Atkins	69f9d2d1e4	website: Link from Configuration index to Resource page ... Since the index page is long, by the time the reader reaches the end of it the relevant portion if the navigation is unlikely to be visible. To compensate for this, we'll link to the first sub-section and thus give the user an opportunity to notice the navigation structure for the rest of the pages.	8 years ago
Martin Atkins	f3f07c120e	website: Fix references to the now-defunct "Interpolation" page ... This has been replaced with an "Expressions" page. Also includes a number of changes to Markdown style to conform to our usual conventions, applied automatically by my editor while making these changes.	8 years ago
Martin Atkins	7805a16172	website: Remove the "interpolation" docs page ... This has now been superseded by the expressions.html.md file in the same directory. As part of deploying this, the former URL for this page must be redirected to the expressions page to retain a target for any existing links on third-party sites.	8 years ago
Martin Atkins	f5e6567f6e	website: Document the JSON configuration syntax	8 years ago
Martin Atkins	71d152c161	website: Expand documentation of Override Files ... This kinda-weird feature was previously quite severely under-documented in terms of exactly what effect it has. This new documentation for it first attempts to frame it as something that should be rarely used, and then explains in more detail exactly how it behaves for different top-level block types within the configuration.	8 years ago
Martin Atkins	150f905be8	website: Update the "Terraform Settings" page for new style ... As part of revamping the "Configuration" portion of the website for the v0.12 release, here we update the Terraform Settings page to use a similar "guide-like" writing style as the other updated pages in this section.	8 years ago
Martin Atkins	676caeabdc	website: Document the index and attribute syntaxes	8 years ago
Martin Atkins	1ee365206a	website: Docs for all of the IP address calculation functions	8 years ago
Martin Atkins	bca602319d	website: Docs for all of the hash/crypto functions	8 years ago
Martin Atkins	425b6adea9	website: Docs for all of the Date and Time functions	8 years ago
Martin Atkins	6903d14f6a	website: Docs for all of the "filesystem" functions	8 years ago
Martin Atkins	0b5bdfbd85	website: Docs for all of the "encoding" functions	8 years ago
Martin Atkins	5f7851ec8b	website: Document the remaining "collection" functions ... This also renames some of the existing function pages whose source filenames were not matching the usual naming scheme (.html.md).	8 years ago
Martin Atkins	edbc87efc2	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	628023036e	website: revisions to the "Configuration Syntax" page and expressions ... This rewrite of the "Configuration Syntax" page now gives some more detail on the top-level structural constructs and de-emphasizes the name "HCL" as subordinate to "the Terraform language". It also now includes some commentary on valid identifiers and comments, and issues around character encodings and line endings. In addition, we now have a new "Expressions" page that replaces the old "Interpolation Syntax" page, covering the expression language features we inherit from HCL and how they behave in the context of Terraform. The "Expressions" page currently links to a page about the built-in functions which does not yet exist. This will be created in a later commit.	8 years ago
Martin Atkins	b5ad292fdf	website: Revise the "Data Sources" configuration docs section ... This adopts a more guide-like writing style, similar to what prior commits have done to some other subsections of this section. The data sources page has not got any real attention since the feature was first added, and our vocabulary for describing them and their lifecycle hadn't quite settled when the page was originally written. This new version is consistent in how it uses "data source" to describe the feature that providers offer and "data resource" to describe what is created by a "data" block in configuration, which then allows us to draw on the many shared features between both data and managed resources. For the moment this waits until "data resource" is defined in order to first introduce the qualifier "managed resource". We may wish to revise this again to mention that more specific nomenclature in passing on the "Resources" page, in case a user encounters it elsewhere and wants to learn what it means without needing to be familiar with data resources first.	8 years ago
Martin Atkins	53a2b3fe8c	website: Revise the "Modules" configuration docs section ... This adopts a more guide-like writing style, similar to what prior commits have done to some other subsections of this section. Since we already have a whole top-level section devoted to modules, there is no need for full coverage of all of their features here. Instead, this section focuses on an an initial introduction to what modules are and the basics of their usage within the Terraform language. We then link to the main modules section for the full details.	8 years ago
Martin Atkins	8ceb97e316	website: Revise the "Local Values" configuration docs section ... This adopts a more guide-like writing style, similar to what prior commits have done to some other subsections of this section.	8 years ago
Martin Atkins	b7c994c919	website: Revise the "Output Values" configuration docs section ... This adopts a more guide-like writing style, similar to what prior commits have done to some other subsections of this section. In the process of writing this, I identified some unclear statements in the "Resources" subsection, and so these are also revised here for consistency with the output values documentation.	8 years ago
Martin Atkins	a349de80e9	website: Revise the "Input Variables" configuration docs section ... This adopts a more guide-like writing style, similar to what prior commits have done to the Resources and Providers sections.	8 years ago
Martin Atkins	f18b1afa80	website: Revise the "Providers" configuration docs section ... These revisions reflect this sub-section's new earlier placement in the sub-section list, leading to a more guide-like style for the initial sections. Also includes some minor copy-editing to align terminology with that introduced in the prior commit for the "Resources" docs page.	8 years ago
Martin Atkins	a8e873a566	website: revise the "Resources" configuration docs section ... This is now the leading subsection of the Configuration section of the docs, and so this rewrite intends to make it more "guide-like" and as accessible as possible to those who are not yet familiar with other Terraform concepts. This rewrite also attempts to introduce some consistency into our vocabulary, which should eventually be reflected throughout our documentation. In particular: - "Resource" refers to the block the user writes in configuration, while "Resource _Type_" refers to what the provider defines. We previously used "resource" for both of these interchangeably. - "Resource" is no longer used to refer to what gets created and managed in remote APIs as a result of a resource block in configuration. Lacking a good distinct name for these, this guide uses the word "object", qualifying it as "infrastructure object" or "remote object" where necessary to retain clarity. This distinction is important to enable a clear description of resource lifecycle. - "Argument" refers to an element (attribute or block) within a resource block. This terminology was already being used in some places, so we embrace it here as a way to distinguish from "attribute", which is what a resource _exports_ for use in expressions. - Since interpolation is no longer needed to use expressions in the language, the word "expression" is used to describe the definition of a value that might involve some computation. Where necessary, this is used with a modifier "arbitrary expression" to contrast with situations where the set of allowed expression constructs is constrained.	8 years ago
Martin Atkins	03ce29f7e5	website: Flesh out the intro to the "Configuration" section. ... The prior content on this page was little more than an instruction to begin navigating the sub-sections of this section. The new content aims to give a broad overview of some of the language concepts and a syntax example, in order to create some context to help the user navigate the subsections more easily. This also introduces for the first time usage of the term "the Terraform language". This was previously left un-named, leading to some awkward sentence constructions elsewhere in the docs. This new name gives us some specific terminology to use in order to contrast the language that exists at Terraform's level of abstraction, defining the semantics, from the underlying grammar provided by HCL.	8 years ago
Martin Atkins	78e67bdb33	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
Martin Atkins	d4ac68423c	website: Tweak the language we use to describe remote state ... After some discussion with "iamakulov" on Twitter it seems that the use of the word "conflicts" and "merge conflicts" here was sounding like us implicitly condoning the use of version control as a mechanism for distributing local state files, which hasn't been recommended for quite some time since remote state now provides a much more robust solution. While here, I also tweaked some other language on this page for style and for use of terminology we more commonly use in our more recent documentation.	8 years ago
Thomas Kula	e2373c8073	website: Using demo.consul.io requires scheme = "https" ... Following the examples as they were previously would cause errors accessing demo.consul.io. Now we consistently set the scheme to https for all examples that use demo.consul.io. This also includes some other updates to the URLs, since the Consul demo has been rebuilt with a different based configuration, and some general formatting and copyediting changes in the Consul example.	8 years ago
Kieran Spear	fa5d9cc2ca	website: Fix spelling mistake (#18311)	8 years ago
Chris Griggs	3b2f747006	Update major-index.html.markdown	8 years ago
Chris Griggs	ac27d7deb9	Update index.html.markdown	8 years ago
Chris	2e9aed6d2b	Add AzureStack documentation links	8 years ago
Quinn Diggity	c943caf1a5	website: fix for typo in resources.html.md (#18266) ... should be provides, not provies	8 years ago
Quinn Diggity	b2df1d424f	website: fixes typo (#18267) ... should be maximum not maxiumum	8 years ago
Paddy	931f8ecc41	Fix broken links to /docs/enterprise/run/api.html ... We had a couple broken links pointing to the docs for the run API. This updates them to the new location.	8 years ago
cabillman	3dc1ce3036	docs: Fix small error in resource targeting docs (#17890)	8 years ago
Peter Hoeg Steffensen	8a5cedaae6	Docs: syntax fix - Removed quotation marks (#18136) ... The example for parsing multiple providers to a module had quotation marks around the keys. This does not seem to be the correct format	8 years ago
Jaye Doepke	596c7b2638	docs typo	8 years ago
SpencerBrown	3324de35b6	Fix typo in doc: "The support operators are" -> "The supported operators are"	8 years ago
Ben Turner	1de8d171ae	Small typo fix	8 years ago
nicklathe	e552897c52	Fix typo (wit -> with) for etcdv3 backend docs	8 years ago
Chris	fba58d3a04	add provider documentation links	8 years ago
Chris	f80aca5d98	add flexibleengine provider documentation links	8 years ago
Chris	c294fd7f1f	remove runscope links	8 years ago
Chris	fbb0c88c21	add runscope provider links	8 years ago
Alexis Grant	170a1530d1	website: Example of the Git+SSH protocol for bitbucket module sources	8 years ago
Chris	ddf5e581ca	add Nutanix	8 years ago