From 65ad73fe034ab7644e8b8a01f8b1b4bf455b3dea Mon Sep 17 00:00:00 2001 From: Martin Atkins Date: Wed, 14 Sep 2022 17:25:42 -0700 Subject: [PATCH] website: Tombstone callout for the v1.3 removed backends We've removed the main documentation pages for the backends that are removed in Terraform v1.3, but we'll leave a small callout note so that the backend names are still reachable through our search index once the v1.3 docs are the active version. The primary goal here is to help folks who have inherited configurations using older versions of Terraform to learn about features they see in those configurations, so the main thing here is the link to the older release docs which include those. However, this is also a good opportunity to link to the upgrade guide content which describes some possible migration paths away from these removed backends. --- website/docs/language/settings/backends/configuration.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/language/settings/backends/configuration.mdx b/website/docs/language/settings/backends/configuration.mdx index f17833c867..bf67313f06 100644 --- a/website/docs/language/settings/backends/configuration.mdx +++ b/website/docs/language/settings/backends/configuration.mdx @@ -18,6 +18,8 @@ By default, Terraform uses a backend called [`local`](/language/settings/backend Some of these backends act like plain remote disks for state files, while others support locking the state while operations are being performed. This helps prevent conflicts and inconsistencies. The built-in backends listed are the only backends. You cannot load additional backends as plugins. +-> **Note:** We removed the `artifactory`, `etcd`, `etcdv3`, `manta`, and `swift` backends in Terraform v1.3. Information about their behavior in older versions is still available in the [Terraform v1.2 documentation](/language/v1.2.x/settings/backends/configuration). For migration paths from these removed backends, refer to [Upgrading to Terraform v1.3](/language/v1.3.x/upgrade-guides). + ## Using a Backend Block You do not need to configure a backend when using Terraform Cloud because