83 Commits (03dc37fda284bc328a04af0d19db077bcfe6ba65)

Author	SHA1	Message	Date
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
Nick Fagerlund	0fddabf972	website: Reorganize nav sidebars to improve jumps between sections	7 years ago
Tom Harvey	ec0419fe91	backend/azurerm: fixing the syntax highlighting (#20085)	7 years ago
Sander van Harmelen	e08a7e979e	backend/remote: use the correct test operation	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
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
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
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
Kristin Laemmert	1be09745d7	Merge pull request #19007 from cardoe/fix-swift-backend-docs ... Fix backend/swift docs	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
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
Henrique M. Gontijo	642cdd331f	Fix typo.	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
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
Paul Tyng	d0fec98833	Merge pull request #18647 from hashicorp/paultyng-patch-1 ... Clarifying the language around "root outputs"	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
Paul Tyng	22bdc44cb1	Clarifying the language around "root outputs"	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
Nick Fagerlund	a51fc61014	website: Revise "atlas" backend page ... Add links to important docs (like user tokens), and explain that this isn't part of our recommended primary workflows anymore.	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
nicklathe	e552897c52	Fix typo (wit -> with) for etcdv3 backend docs	8 years ago
Andrew Haines	b6fbb42be6	Add required DynamoDB IAM permissions for state locking to S3 backend docs	8 years ago
Andrew Haines	6c2b2515bd	Update reference to deprecated argument in S3 backend docs	8 years ago
Logan Rakai	dd935588f7	Typo Correction	8 years ago
James Bardin	5458ea9aff	update etcd documentation links ... Add missing link to ectdv3. Update etcd v2 link to the current v2 README, which highlights the pending deprecation.	8 years ago
Harry Mills	856b852ac2	Correct typo	8 years ago
Paddy	e4cdbd6c9f	Merge pull request #16936 from negz/gcskeys ... Support 'customer supplied encryption keys' in the GCS backend	8 years ago
James Bardin	d1a678db0d	Merge pull request #16915 from hashicorp/jbardin/gcs-docs ... add gcs to the backends that support workspaces in the documentation	8 years ago
Paul Stack	191cf283d5	backend/manta: Support Triton RBAC ... Triton Manta allows an account other than the main triton account to be used via RBAC. Here we expose the SDC_USER / TRITON_USER options to the backend so that a user can be specified.	8 years ago
Nic Cope	011841124b	Support 'customer supplied encryption keys' in the GCS backend ... https://cloud.google.com/storage/docs/encryption#customer-supplied GCS state created using customer supplied encryption keys can only be read or modified using the same key.	8 years ago
James Bardin	ccb90d5b6b	add gcs to the backends that support workspaces ... Also add the term "workspaces" to the `prefix` documentation.	8 years ago
Martin Atkins	c729bdff43	website: guide for using the S3 backend with multiple AWS accounts ... Users commonly ask how the S3 backend can be used in an organization that splits its infrastructure across many AWS accounts. We've traditionally shied away from making specific recommendations here because we can't possibly anticipate the different standards and regulations that constrain each user. This new section attempts to describe one possible approach that works well with Terraform's workflow, with the goal that users make adjustments to it taking into account their unique needs. Since we are intentionally not being prescriptive here -- instead considering this just one of many approaches -- it deviates from our usual active writing style in several places to avoid giving the impression that these are instructions to be followed exactly, which in some cases requires the use of passive voice even though that is contrary to our documentation style guide. For similar reasons, this section is also light on specific code examples, since we do not wish to encourage users to just copy-paste the examples without thinking through the consequences.	8 years ago