terraform

Commit Graph

Author	SHA1	Message	Date
Brian Flad	185a3304e5	Merge pull request #20374 from hashicorp/td-backend-s3-dependencies backend/s3: Switch from github.com/terraform-providers/terraform-provider-aws to github.com/hashicorp/aws-sdk-go-base	7 years ago
Paddy	1bef862e3a	Merge pull request #18972 from rileykarson/patch-2 Fix Google Cloud Platform name across docs	7 years ago
Brian Flad	1aaac172b0	backend/s3: Switch from github.com/terraform-providers/terraform-provider-aws to github.com/hashicorp/aws-sdk-go-base Output from acceptance testing (no new failures): ``` --- PASS: TestBackend_impl (0.00s) --- PASS: TestBackendConfig (0.37s) --- PASS: TestBackendConfig_invalidKey (0.00s) --- PASS: TestBackend (3.26s) --- PASS: TestBackendLocked (6.80s) --- FAIL: TestBackendExtraPaths (2.32s) --- PASS: TestBackendPrefixInWorkspace (2.06s) --- PASS: TestKeyEnv (8.20s) --- PASS: TestRemoteClient_impl (0.00s) --- PASS: TestRemoteClient (2.42s) --- PASS: TestRemoteClientLocks (6.33s) --- PASS: TestForceUnlock (13.31s) --- PASS: TestRemoteClient_clientMD5 (11.75s) --- PASS: TestRemoteClient_stateChecksum (10.07s) ```	7 years ago
Martin Atkins	b4d9f63622	website: Forward-port docs on file-hashing functions from 0.11 branch	7 years ago
cgriggs01	1565abfcaa	add four community providers	7 years ago
cgriggs01	41af6ce54b	two new community providers	7 years ago
Laura Martin	76dedfbf9d	Update docs for 0.12 terraform_remote_state data source In 0.12, the outputs for a data source of terraform_remote_state are nested under the 'outputs' attribute [1]. This updates the docs to make this change clearer. Worked with @radeksimko at Terraform hackday, who has submitted a related upgrade guide [2] [1] `1f4d2f4c50/builtin/providers/terraform/data_source_state.go (L16-L43)` [2] `d8e00191b7`	7 years ago
cgriggs01	4db4f9102d	change plath name	7 years ago
Nick Fagerlund	58289e2d90	website: Change absolute 0.11 -> 0.11 links to relative	7 years ago
Nick Fagerlund	2c50808bbb	website: Version notes: Add new -> old links to 0.12 language docs (function pages)	7 years ago
Nick Fagerlund	4a190127b9	website: Version notes: Add new -> old links to 0.12 language docs (except function pages)	7 years ago
Nick Fagerlund	9ce8e0ee18	website: Version notes: Add old -> new links to 0.11 docs	7 years ago
Nick Fagerlund	b726cc4ba9	website: Update H1 header of 0.12 index.html	7 years ago
Nick Fagerlund	2dcd4a886f	website: Standardize page titles in 0.11 language docs	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
Tom Harvey	ec0419fe91	backend/azurerm: fixing the syntax highlighting (#20085 )	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
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.	7 years ago
Sander van Harmelen	e08a7e979e	backend/remote: use the correct test operation	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
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	7 years ago
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
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	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

1 2 3 4 5 ...

433 Commits (6cc3e1d0bd635cdae92b3e0055c19d86dfa7a222)