373 Commits (e95f2b586e744dfb0cf92352de491be8a09552c2)

Author	SHA1	Message	Date
Kristin Laemmert	1be09745d7	Merge pull request #19007 from cardoe/fix-swift-backend-docs ... Fix backend/swift docs	7 years ago
Nick Fagerlund	3b02214d8c	website: clarify behavior of terraform_remote_state data sources (#19227)	7 years ago
Tom Harvey	49c42b9830	docs: add warning to backend/swift about auto-expire ... If the user uses the auto-expire value in the backend/swift settings then swift will automatically delete their Statefile which is likely something the user doesn't want given how Terraform works.	7 years ago
Doug Goldstein	817be7b23f	website: update backend/swift examples to use versioning ... Since object versioning is a best practice the docs should have all the examples containing it by default.	7 years ago
Doug Goldstein	58cb47d108	website: backend/swift fix bad link for object versioning ... The displayed link said `expire_after` but really is a link to `archive_container` so update the link to read the right data. fixes #19005	7 years ago
Doug Goldstein	ddc30b6546	website: backend/swift add docs link for expire_after ... Provide a link to the OpenStack Swift docs for the object expiration feature that is used by the `expire_after` field.	7 years ago
Doug Goldstein	b31aab4469	website: fix backend/swift links to Swift docs ... The links to the OpenStack Swift documentation were broken due to changes on the OpenStack website.	7 years ago
Doug Goldstein	027b107268	website: update deprecated backend/swift docs ... Update the examples and docs to not directly reference deprecated fields.	7 years ago
Sander van Harmelen	52a1b22f7a	Implement the remote enhanced backend ... This is a refactored version of the `remote` backend that was initially added to Terraform v0.11.8 which should now be compatible with v0.12.0.	7 years ago
Sean Carolan	b7cf7737f6	website: use a clearer header describing the CLI config file (#19263) ... Using a / could be confusing to users who assume it is a directory.	7 years ago
Sander van Harmelen	178ec8f7b4	Remove support for the -module-depth flag ... # Conflicts: # backend/backend.go	7 years ago
cgriggs01	06a74a2dac	fixit	7 years ago
cgriggs01	56a16e57a9	another provider and edit	7 years ago
cgriggs01	46c36b5e72	adding two community	7 years ago
Nick Fagerlund	ab88f8ca0f	website: Update and link the page about remote backend operations (#19203)	7 years ago
Kristin Laemmert	5fa624c55e	website: update terraform_remote_state syntax in backend docs	7 years ago
Radek Simko	b54cc1d95f	Merge pull request #19170 from mikesir87/patch-1 ... Small grammar fix for lifecycle docs	8 years ago
Michael Irwin	47047aa637	Small grammar fix for lifecycle docs	8 years ago
Henrique M. Gontijo	642cdd331f	Fix typo.	8 years ago
Chris Griggs	c98f2087fb	Merge pull request #19105 from cgriggs01/cgriggs01-linode-2 ... [Website] Linode documentation links	8 years ago
cgriggs01	a48dda2acc	add linode documentation links	8 years ago
Radek Simko	edaa4bbc82	lang: Add fileexists function	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
Kristin Laemmert	b6d3d69d3a	port cidr functions	8 years ago
Kristin Laemmert	602b59cdc4	porting functions	8 years ago
Kristin Laemmert	9aa9b18658	porting crypto functions	8 years ago
Kristin Laemmert	1a5299efcb	porting encoding functions	8 years ago
Martin Atkins	60ad24229f	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	b2e8987f7e	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	6549f24d88	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	c060ecd0a5	website: Document the JSON configuration syntax	8 years ago
Martin Atkins	a6749f9efc	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	b3239e8f1f	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	d72d9fde16	website: Document the index and attribute syntaxes	8 years ago
Martin Atkins	83a16e3deb	website: Docs for all of the IP address calculation functions	8 years ago
Martin Atkins	7cb1de9f30	website: Docs for all of the hash/crypto functions	8 years ago
Martin Atkins	46f8208727	website: Docs for all of the Date and Time functions	8 years ago
Martin Atkins	a35c0f3cbf	website: Docs for all of the "filesystem" functions	8 years ago
Martin Atkins	a491013054	website: Docs for all of the "encoding" functions	8 years ago
Martin Atkins	e7d71995f6	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	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	39579e8d0f	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	e1754970a8	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	eeb96b1e12	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	fdc8bb6c00	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	e41883d972	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	f8f2ff2202	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	a6cf796873	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	6fa6a0d110	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	27429b61a9	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