From d65fb742be4ce30878d40c35aeb660ecbf6c864b Mon Sep 17 00:00:00 2001 From: Oleksandr Levchenkov Date: Tue, 30 Jul 2024 10:22:10 +0300 Subject: [PATCH] add clarification on remote vs remote state backends (#1851) Signed-off-by: ollevche Signed-off-by: Oleksandr Levchenkov Co-authored-by: Christian Mesh Co-authored-by: Janos <86970079+janosdebugs@users.noreply.github.com> --- website/docs/language/settings/backends/remote.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/website/docs/language/settings/backends/remote.mdx b/website/docs/language/settings/backends/remote.mdx index f80f67ca4d..adb405ade2 100644 --- a/website/docs/language/settings/backends/remote.mdx +++ b/website/docs/language/settings/backends/remote.mdx @@ -7,8 +7,11 @@ description: >- # Backend Type: remote +Most of the available backends provide different ways of storing state snapshots remotely. Therefore, they are often called remote state backends. +This page describes a special `remote` backend, not to be confused with the simpler remote state backends. + :::note -**We recommend using the [`cloud` built-in integration](../../../cli/cloud/settings.mdx)** instead of this backend. The `cloud` option includes an improved user experience and more features. +**We recommend using the [`cloud` built-in integration](../../../cli/cloud/settings.mdx)** instead of the `remote` backend. The `cloud` option includes an improved user experience and more features. ::: The remote backend is unique among all other OpenTofu backends because it can both store state snapshots and execute CLI-driven run workflow operations for TF Automation and Collaboration Software ([TACOS](../../../intro/tacos.mdx)) backends. It used to be called an "enhanced" backend.