mirror of
https://github.com/opentffoundation/opentf.git
synced 2026-02-18 13:00:36 -05:00
f521ba6cd7
As explained in the changes: The 'enhanced' backend terminology, which only truly pertains to the 'remote' backend with a single API (Terraform Cloud/Enterprise's), has been found to be a confusing vestige which need only be explained in the context of the 'remote' backend. These changes reorient the explanation(s) of backends to pertain more directly to their primary purpose, which is storage of state snapshots (and not implementing operations). That Terraform operations are still _implemented_ by the literal `Backend` and `Enhanced` interfaces is inconsequential a user of Terraform, an internal detail.
1.0 KiB
1.0 KiB
layout, page_title, sidebar_current, description
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| language | Backend Type: etcd | docs-backends-types-standard-etcdv2 | Terraform can store state remotely in etcd 2.x. |
etcd
Stores the state in etcd 2.x at a given path.
This backend does not support state locking.
Example Configuration
terraform {
backend "etcd" {
path = "path/to/terraform.tfstate"
endpoints = "http://one:4001 http://two:4001"
}
}
Data Source Configuration
data "terraform_remote_state" "foo" {
backend = "etcd"
config = {
path = "path/to/terraform.tfstate"
endpoints = "http://one:4001 http://two:4001"
}
}
Configuration variables
The following configuration options are supported:
path- (Required) The path where to store the stateendpoints- (Required) A space-separated list of the etcd endpointsusername- (Optional) The usernamepassword- (Optional) The password