jprdonnelly/opentf
1
0
Fork 0
mirror of https://github.com/opentffoundation/opentf.git synced 2025-12-19 17:59:05 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update JSON syntax documentation for variables in module & terraform blocks (#3587)

Browse Source 
Signed-off-by: H.K. <angivare-contact@yahoo.fr>
Signed-off-by: Christian Mesh <christianmesh1@gmail.com>
This commit is contained in:
H.K.
2025-12-15 13:54:55 +01:00
committed by Christian Mesh
parent 3d3dc740e1
commit aa426611d9
1 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
website/docs/language/syntax/json.mdx
View File

@@ -409,9 +409,6 @@ The value of each of these nested properties is
### `module` blocks
The `source` and `version` meta-arguments must be given as literal strings. The
values are not interpreted as string templates.
The `providers` meta-argument must be given as a JSON object whose properties
are the compact provider addresses to expose into the child module and whose
values are the provider addresses to use from the current module, both
@@ -454,9 +451,10 @@ values are not interpreted as string templates.
### `terraform` blocks
Since no settings within `terraform` blocks accept named object references or
function calls, all setting values are taken literally. String values are not
interpreted as string templates.
Settings within `terraform` blocks are generally interpreted literally, except
for the `backend` block, which supports expressions. Other settings do not
accept named object references or function calls and therefore do not treat
string values as string templates.
Since only one `backend` block is allowed per `terraform` block, the compact
block mapping can be used to represent it, with a nested object containing