terraform

Commit Graph

Author	SHA1	Message	Date
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
Kevin Fishner	3538f832b0	website: update "atlas" backend to recommend using ATLAS_TOKEN environment variable	8 years ago
Andrew	d6b8e27086	website: Document required S3 IAM actions for S3 backend	8 years ago
Sander van Harmelen	aaedf255c3	backend/s3: allow skipping the region check (#16757 ) Without the possibility to skip this check, it’s not possible to use a custom region with a third-party service that mimicks the S3 API.	8 years ago
Dominik Lekse	323654a716	Fixed documentation of azurerm backend advanced access variables (#16552 ) Signed-off-by: Dominik Lekse <dominik@lekse.de>	8 years ago
stack72	1fd0f803e4	Migrate Manta Remote state to be a backend This PR changes manta from being a legacy remote state client to a new backend type. This also includes creating a simple lock within manta This PR also unifies the way the triton client is configured (the schema) and also uses the same env vars to set the backend up It is important to note that if the remote state path does not exist, then the backend will create that path. This means the user doesn't need to fall into a chicken and egg situation of creating the directory in advance before interacting with it	9 years ago
Greg Oliver	b5d3559d2d	website: refine the description of the azurerm backend	9 years ago
Florian Forster	927085289d	backend/remote-state/gcs: Implement the "region" config option. This allows to select the region in which a bucket is created. This copies behavior from the Google Cloud provider.	9 years ago
Florian Forster	9583d0945c	backend/remote-state/gcs: Add support for the GOOGLE_PROJECT environment variable. This copies behavior from the Google Cloud provider.	9 years ago
Florian Forster	52e6159219	backend/remote-state/gcs: Improve "bucket" and "credentials" documentation.	9 years ago
Florian Forster	df386d3133	backend/remote-state/gcs: Automatically create the bucket if needed. This resurrects the previously documented but unused "project" option. This option is required to create buckets (so they are associated with the right cloud project) but not to access the buckets later on (because their names are globally unique).	9 years ago
Florian Forster	5205c63bc9	website/docs/backends/types/gcs.html.md: Update. * Remove the (unused) "project" option. * Mark the "credentials" option as optional; document behavior when unset. * Mark the "path" option as deprecated (was: legacy) to match Terraform's terminology.	9 years ago
Florian Forster	14bfbf0617	backend/remote-state/gcs: Document the "prefix" option. "state_dir" has been renamed to "prefix" to better fix the GCS terminology.	9 years ago
James Bardin	91442b7146	Merge pull request #15680 from brunomcustodio/etcdv3-backend [WIP] etcd v3 backend with lock support.	9 years ago
James Bardin	d477d1f6d4	Merge pull request #15553 from bonifaido/custom_s3_backend Allow non-AWS S3 backends	9 years ago
Bruno Miguel Custodio	524c3934c6	Add TLS support.	9 years ago
Bruno Miguel Custodio	6daf1d9d84	Allow for username and password to be read from envvars.	9 years ago
Bruno Miguel Custodio	8f7b315037	Add documentation.	9 years ago
Tom Harvey	cbb512d374	Updating the AzureRM Backend Documentation (#15990 ) * Updating to reference this has been renamed * Clarifying Blob Storage	9 years ago
Loïc Albertin	21b287e919	backend/consul: allow specifying various Consul client security options These new options are equivalent to the consul CLI arguments -ca-file, -client-cert and -client-key.	9 years ago
Martin Atkins	2e0c1d07ae	Merge #15793 : Locking support in HTTP remote backend	9 years ago
Ross McFarland	e5029de439	Update remote/http doc to match locking changes	9 years ago
James Bardin	216a68a41b	update backend docs to reflect new azurerm name The backend has been renamed. Using the old name in the config will trigger a deprecation warning, but the implementation and the documentation is the same.	9 years ago
Peter McAtominey	f9e8e54835	backend: convert Azure remote state to a backend Added locking support via blob leasing (requires that an empty state is created before any lock can be acquired. Added support for "environments" in much the same way as the S3 backend.	9 years ago
Tom Harvey	81f9c78122	Adding `resource_group_name` back in, fixes #15610 (#15809 )	9 years ago
Ross McFarland	06b4b509d7	Doc state/http supports_locking	9 years ago
James Bardin	f63b216016	Update S3 backend docs to reflect new workspaces Explain the path generated for state files when using workspaces.	9 years ago
Martin Atkins	23ef0e3247	website: more-elaborate "terraform init" docs The "terraform init" command has a lot of different functionality now, making it hard to follow all of the options in the previous presentation. Instead, here we describe each of the steps and its associated options separately, hopefully making it easier to understand what each option relates to. In addition, much of the detail around backend partial configuration is factored out into the backend configuration page, where it seems more "at home"; previously it felt hard to follow exactly how partial configuration would be used, due to the information on it being split over two different pages.	9 years ago
Nandor Kracser	f6c77339f2	Allow non-AWS S3 backends This commit makes sts, metadata and other AWS related API calls optional, thus the backend initialization will not send non-AWS API tokens to AWS APIs	9 years ago
James Bardin	5066fa2151	Merge pull request #13871 from fatmcgav/swift_move_to_backend Move Swift remote state to backend	9 years ago
Thomas Schaaf	4b85e91ac5	Update s3.html.md (#15299 )	9 years ago
Alex Rowley	22f36a6e43	Document new field for S3 backend	9 years ago
Gavin Williams	af5467b9fd	website: Update swift backend documentation	9 years ago
Martin Atkins	7ed70bb00e	website: new filesystem layout for core/provider split This repo now contains only the core docs, with other content moving elsewhere.	9 years ago

40 Commits (1e12e498784c1cd89d9135ffbda47e89ddcfcfdf)