525 Commits (e024960c745f0a464cb081d04765d93f94deaba0)

Author	SHA1	Message	Date
Nick Fagerlund	2c50808bbb	website: Version notes: Add new -> old links to 0.12 language docs (function pages)	8 years ago
Nick Fagerlund	4a190127b9	website: Version notes: Add new -> old links to 0.12 language docs (except function pages)	8 years ago
Nick Fagerlund	9ce8e0ee18	website: Version notes: Add old -> new links to 0.11 docs	8 years ago
Nick Fagerlund	b726cc4ba9	website: Update H1 header of 0.12 index.html	8 years ago
Nick Fagerlund	2dcd4a886f	website: Standardize page titles in 0.11 language docs	8 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.	8 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.	8 years ago
Nick Fagerlund	0fddabf972	website: Reorganize nav sidebars to improve jumps between sections	8 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.	8 years ago
Tom Harvey	ec0419fe91	backend/azurerm: fixing the syntax highlighting (#20085)	8 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.	8 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.	8 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.	8 years ago
Riley Karson	74ec68f9d4	Fix Google Cloud Platform name across docs. ... The `google` provider supports GCP, not necessarily Google Cloud as a whole. Update the naming on this index page to match [the provider README](https://github.com/terraform-providers/terraform-provider-google#terraform-provider-for-google-cloud-platform) and the [provider docs changes](https://github.com/terraform-providers/terraform-provider-google/blob/master/website/docs/index.html.markdown#google-cloud-platform-provider) coming in the next release.	8 years ago
Sander van Harmelen	e08a7e979e	backend/remote: use the correct test operation	8 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.	8 years ago
Scott Stevenson	cef46ef953	Add details about using lock=true when consul ACL is enabled ... This PR addresses https://github.com/hashicorp/terraform/issues/19963.	8 years ago
Brian Flad	05691a978e	Merge pull request #19951 from hashicorp/s3-backend-nosuchbucket-enhanced-error ... backend/s3: Configure AWS Client MaxRetries and provide enhanced S3 NoSuchBucket error message	8 years ago
Chris Griggs	0cc057b873	Merge branch 'master' into cgriggs01-comm-5	8 years ago
Tom Harvey	177ca3711d	Adding the AzureAD entry to the providers page (#19946) ... Adding the AzureAD entry to the providers page	8 years ago
cgriggs01	a9069cab7b	edit fmt	8 years ago
cgriggs01	885a366f2e	add <tr>	8 years ago
cgriggs01	830e23b217	add new community providers	8 years ago
Brian Flad	ed37d07632	backend/s3: Configure AWS Client MaxRetries and provide enhanced S3 NoSuchBucket error message ... The AWS Go SDK automatically provides a default request retryer with exponential backoff that is invoked via setting `MaxRetries` or leaving it `nil` will default to 3. The terraform-aws-provider `config.Client()` sets `MaxRetries` to 0 unless explicitly configured above 0. Previously, we were not overriding this behavior by setting the configuration and therefore not invoking the default request retryer. The default retryer already handles HTTP error codes above 500, including S3's InternalError response, so the extraneous handling can be removed. This will also start automatically retrying many additional cases, such as temporary networking issues or other retryable AWS service responses. Changes: * s3/backend: Add `max_retries` argument * s3/backend: Enhance S3 NoSuchBucket error to include additional information	8 years ago
Kristin Laemmert	cdf7cc2449	command/json*: updating documentation and adding tests (#19944) ... A few minor fixes and cleanups as a result of said tests. Hooray for eventual consistency!	8 years ago
Martin Atkins	d0e6a4c69a	lang: Add "formatdate" function ... We missed this one on a previous pass of bringing in most of the cty stdlib functions. This will resolve #17625 by allowing conversion from Terraform's conventional RFC 3339 timestamps into various other formats.	8 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.	8 years ago
Nick Fagerlund	17873ae61b	website: Update functions section page titles	8 years ago
Nick Fagerlund	9f85e6d5cc	website: Update configuration language section page titles	8 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.	8 years ago
cgriggs01	da370cd689	fix spacing in website docs	8 years ago
cgriggs01	9df6e2df42	add hedvig provider links	8 years ago
cgriggs01	79f93ed695	links for ucloud provider	8 years ago
Sander van Harmelen	da8e02eb2e	Merge pull request #19647 from hashicorp/svh/f-versions ... core: add a method to the disco package retrieve version constraints	8 years ago
Sander van Harmelen	268c0f85ce	Add a method to retrieve version contraints	8 years ago
Brian Flad	058434d28b	Merge pull request #19571 from hashicorp/f-backend-s3-other-endpoints ... backend/s3: Support DynamoDB, IAM, and STS endpoint configurations	8 years ago
Tom Harvey	383bc98f5c	backend/azurerm: Support for authenticating using the Azure CLI (#19465) ... * Upgrading to 2.0.0 of github.com/hashicorp/go-azure-helpers * Support for authenticating using Azure CLI * backend/azurerm: support for authenticating using the Azure CLI	8 years ago
cgriggs01	41897bb437	six new community providers	8 years ago
Brian Flad	9a3b02cd6c	backend/s3: Support DynamoDB, IAM, and STS endpoint configurations ... This change enables a few related use cases: * AWS has partitions outside Commercial, GovCloud (US), and China, which are the only endpoints automatically handled by the AWS Go SDK. DynamoDB locking and credential verification can not currently be enabled in those regions. * Allows usage of any DynamoDB-compatible API for state locking * Allows usage of any IAM/STS-compatible API for credential verification	8 years ago
cgriggs01	808c76fa9b	Add skytap links	8 years ago
Chris Griggs	89347e9c81	Updates path name	8 years ago
cgriggs01	c943083a4b	selvpc -> selectel	8 years ago
Daniel Schroeder	65080b9ce3	website: Fix redundant "be" in workspaces documentation	8 years ago
Chris Griggs	e32c5de440	Merge pull request #19390 from cgriggs01/cgriggs01-selvpc ... [Website] New certified and community provider	8 years ago
cgriggs01	f013942150	formatting edits	8 years ago
Tom Harvey	6d4f702467	backend/azurerm: support for custom resource manager endpoints (#19460) ... * backend/azurerm: removing the `arm_` prefix from keys * removing the deprecated fields test because the deprecation makes it fail * authentication: support for custom resource manager endpoints * Adding debug prefixes to the log statements	8 years ago
Tom Harvey	d580f30e03	backend/azurerm: removing the `arm_` prefix from keys (#19448) ... * backend/azurerm: removing the `arm_` prefix from keys * removing the deprecated fields test because the deprecation makes it fail	8 years ago
Tom Harvey	96b1c951fa	backend/azurerm: support for authenticating via SAS Tokens (#19440) ... * adding acceptance tests for msi auth * including the resource group name in the tests * backend/azurerm: support for authenticating using a SAS Token * resolving merge conflicts * moving the defer to prior to the error	8 years ago
Tom Harvey	c928962f44	backend/azurerm: support for authenticating via msi (#19433) ... * backend/azurerm: support for authenticating via msi * adding acceptance tests for msi auth * including the resource group name in the tests * support for using the test client via msi	8 years ago
Tom Harvey	0ec109bdc0	backend/azurerm: upgrading the SDK / support for proxies (#19414) ... * vendor updates - updating to v21.3.0 of github.com/Azure/azure-sdk-for-go - updating to v10.15.4 of github.com/Azure/go-autorest - vendoring github.com/hashicorp/go-azure-helpers @ 0.1.1 * backend/azurerm: refactoring to use the new auth package - refactoring the backend to use a shared client via the new auth package - adding tests covering both Service Principal and Access Key auth - support for authenticating using a proxy - rewriting the backend documentation to include examples of both authentication types * switching to use the build-in logging function * documenting it's also possible to retrieve the access key from an env var	8 years ago
Nick Fagerlund	7d5db9522f	website: Fix plugin path on Windows (#19423) ... ...and one other reference to the application data directory. Context: https://docs.microsoft.com/en-us/windows/desktop/shell/knownfolderid#folderid_roamingappdata In newer Windows versions, the folder accessible as `%APPDATA%` (and via various APIs) is actually at something like "documents and settings\user\application data\roaming", while earlier versions omit the "\roaming" part of the path. This means you can confuse people by referring to the "application data" directory by its human name, because "roaming" is the real application data directory, but it looks like a subdirectory of "application data". Thus, it's less confusing to just use the `%APPDATA%` variable, with the added benefit that you can copy and paste the path and it'll just work in most places.	8 years ago
cgriggs01	28de3823ac	new provider and community links	8 years ago
Kristin Laemmert	1be09745d7	Merge pull request #19007 from cardoe/fix-swift-backend-docs ... Fix backend/swift docs	8 years ago
Nick Fagerlund	3b02214d8c	website: clarify behavior of terraform_remote_state data sources (#19227)	8 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.	8 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.	8 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	8 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.	8 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.	8 years ago
Doug Goldstein	027b107268	website: update deprecated backend/swift docs ... Update the examples and docs to not directly reference deprecated fields.	8 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.	8 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.	8 years ago
Sander van Harmelen	178ec8f7b4	Remove support for the -module-depth flag ... # Conflicts: # backend/backend.go	8 years ago
cgriggs01	06a74a2dac	fixit	8 years ago
cgriggs01	56a16e57a9	another provider and edit	8 years ago
cgriggs01	46c36b5e72	adding two community	8 years ago
Nick Fagerlund	ab88f8ca0f	website: Update and link the page about remote backend operations (#19203)	8 years ago
Kristin Laemmert	5fa624c55e	website: update terraform_remote_state syntax in backend docs	8 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
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
Sander van Harmelen	775f8a9626	Make sure we always set a custom header ... This is for TFE to recognize were the calls come from.	8 years ago
cgriggs01	87191d46cd	add helm links	8 years ago
cgriggs01	24c360ec8d	add nutanix links	8 years ago
Chris Griggs	9463b010ed	Spelling fix!	8 years ago
cgriggs01	7119caf198	formatting	8 years ago
cgriggs01	4bee6b30e2	add community prov	8 years ago
Nick Fagerlund	b3935b29d7	website: Reconcile docs about plugin discovery and downloading (#18973) ... website: Reconcile docs about plugin discovery and downloading I'm attempting to keep things simple for normal users while making sure we've got the full behavior written down somewhere for plugin developers. This commit doesn't stand alone; it's paired with a commit in the terraform-website repo, to deal with some related content in the "extend" section.	8 years ago
cgriggs01	8bce8cd72a	fix typo	8 years ago
cgriggs01	009ede44e2	add community providers	8 years ago
cgriggs01	2d7b9dfcf9	add tencentclould links	8 years ago
cgriggs01	fc3148e17a	add bigip links	8 years ago
Radek Simko	ecac80fd8e	docs: Fix inaccurate plugin CRUD description	8 years ago
otofune	2a902fc06d	Fix proper nouns of vcs services	8 years ago
Chris Griggs	735e38916a	CamelCase!	8 years ago
Chris Griggs	08c407a468	Merge branch 'master' into cgriggs01-rightscale	8 years ago
Chris Griggs	28ef7e2d37	Update	8 years ago
Chris Griggs	daf1ec607d	CamelCase	8 years ago
Chris Griggs	a7e5e15dc1	CamelCase it!	8 years ago
cgriggs01	7244abd978	add rightscale provider links	8 years ago
cgriggs01	a1b08e16c3	add oci provider links	8 years ago
cgriggs01	d6acc463e5	update community providers	8 years ago
Chris Griggs	6841414632	Merge pull request #18854 from cgriggs01/netlify-release ... add Netlify provider links	8 years ago
Kristin Laemmert	19f56e3cb4	Merge pull request #18829 from saravanan30erd/issue-18808 ... issue #18808 docs: update uuid definition - UUID is *not* in in RFC 4122 v4 format.	8 years ago
cgriggs01	43ff5e445a	add Netlify provider links	8 years ago
Chris Doherty	71c79522c6	website: Add docs/internals/archiving.html to describe the archiving process. (#18831) ... Add docs/internals/archiving.html to describe the archiving process.	8 years ago
saravanan palanisamy	517e28ee6e	update uuid definition	8 years ago
Dave Wongillies	9190227bc0	Fix description for state mv and push sub-commands	8 years ago
HashiBook1000	d9823d7c8b	add HuaweiCloud link	8 years ago
Sander van Harmelen	77b9fad7f0	backend/manta: deprecate camelcase attribute name ... This change is needed (next to making it consistent as its the only attribute name that uses camelcase) because passing that attribute objectName in the update `terraform_remote_state` resource, ended up giving me this error: https://github.com/hashicorp/terraform/blob/master/helper/schema/schema.go#L736	8 years ago
Paul Hinze	cf8516287e	website: Classify remote backends as a preview release	8 years ago
Alexis Grant	6e5259911e	PTFE not ready for use with this remote version	8 years ago
Nick Fagerlund	4612a71414	website: revise docs for remote backend and credentials config	8 years ago
Phillip Wong	6b89588154	Correction of spelling for 'Keboola' provider ... I also switched it around with the Kafka link to preserve the alphabetical ordering of the page.	8 years ago
HashiBook1000	c612953a72	add community providers, remove Atlas links	8 years ago
Paul Tyng	d0fec98833	Merge pull request #18647 from hashicorp/paultyng-patch-1 ... Clarifying the language around "root outputs"	8 years ago
Chris Griggs	4bbf303f72	Update infra-index.html.markdown	8 years ago
HashiBook1000	3a75b28626	swap tfe v2 links with Atlas	8 years ago
Sander van Harmelen	bb37637a13	Merge pull request #18642 from hashicorp/f-remote-backend ... backend/remote: do not use the TFE_TOKEN env variable	8 years ago
Sander van Harmelen	7049d973a9	Do not use the TFE_TOKEN env variable ... Instead promote the use of shared credentials using the CLI Config File	8 years ago
HashiBook1000	fc6671e191	fix ACME link and add community providers	8 years ago
Paul Tyng	22bdc44cb1	Clarifying the language around "root outputs"	8 years ago
HashiBook1000	8042a96ff7	update master with provider links	8 years ago
Sander van Harmelen	7fb2d1b8de	Implement the Enterprise enhanced remote backend	8 years ago
Nick Fagerlund	2487af1945	website: atlas backend requires https protocol in address (#18585) ... Just providing the hostname won't work. This commit adds an example and fixes the explanation.	8 years ago
Phillip Wong	6699321802	Update community-index.html.markdown ... Corrected the naming of the 'Keboola' provider and shifted it down to keep alphabetical ordering.	8 years ago
Martin Atkins	15ad2e4f9e	website: Revise the "Module Sources" page ... It's been a while since we made any significant updates to this page. The main theme of this revamp is to ensure that we highlight how to provide "ambient credentials" for each of the module sources using the standard mechanisms for each source type. While there, I also attempted a general cleanup to highlight the main cases and make this less like a detailed description of all of go-getter's esoteric features, and did some general copy-editing to write it in our usual documentation "voice".	8 years ago
Alexis Grant	c97a4246ff	website: update module creation docs to link to version constraint info	8 years ago