406 Commits (bc5eecd7f2e9fd261a980e911bb92f3bb8dd985a)

Author	SHA1	Message	Date
Chris Griggs	0cc057b873	Merge branch 'master' into cgriggs01-comm-5	7 years ago
Tom Harvey	177ca3711d	Adding the AzureAD entry to the providers page (#19946) ... Adding the AzureAD entry to the providers page	7 years ago
cgriggs01	a9069cab7b	edit fmt	7 years ago
cgriggs01	885a366f2e	add <tr>	7 years ago
cgriggs01	830e23b217	add new community providers	7 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!	7 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.	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	17873ae61b	website: Update functions section page titles	7 years ago
Nick Fagerlund	9f85e6d5cc	website: Update configuration language section page titles	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
cgriggs01	da370cd689	fix spacing in website docs	7 years ago
cgriggs01	9df6e2df42	add hedvig provider links	7 years ago
cgriggs01	79f93ed695	links for ucloud provider	7 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	7 years ago
Sander van Harmelen	268c0f85ce	Add a method to retrieve version contraints	7 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	7 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	7 years ago
cgriggs01	41897bb437	six new community providers	7 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	7 years ago
cgriggs01	808c76fa9b	Add skytap links	7 years ago
Chris Griggs	89347e9c81	Updates path name	7 years ago
cgriggs01	c943083a4b	selvpc -> selectel	7 years ago
Daniel Schroeder	65080b9ce3	website: Fix redundant "be" in workspaces documentation	7 years ago
Chris Griggs	e32c5de440	Merge pull request #19390 from cgriggs01/cgriggs01-selvpc ... [Website] New certified and community provider	7 years ago
cgriggs01	f013942150	formatting edits	7 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	7 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	7 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	7 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	7 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	7 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.	7 years ago
cgriggs01	28de3823ac	new provider and community links	7 years ago
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.	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