Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify use of backend-config file #35389

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Clarify use of backend-config file #35389

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4ee061c
Clarify use of backend-config file
asmacdo Jun 26, 2024
e0481ea
Update website/docs/language/settings/backends/configuration.mdx
asmacdo Jun 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions website/docs/language/settings/backends/configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -156,6 +156,17 @@ naming pattern. Terraform will not prevent you from using other names but follow
this convention will help your editor understand the content and likely provide
better editing experience as a result.

- Using a backend configuration file or CLI key-value pairs overrides the contents,
but not the type of `backend`. (e.g. Use a Partial Configuration in the primary config.)

```hcl
terraform {
backend {
# values provided by backend-config file
}
}
```

### Command-line key/value pairs

The same settings can alternatively be specified on the command line as
Expand Down
Loading