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

Change docs links: /opentf-> /docs (#367)

Browse Source 
Signed-off-by: Roman Grinovski <roman.grinovski@gmail.com>
This commit is contained in:
Roman Grinovski
2023-09-15 14:10:27 +02:00
committed by GitHub
parent bb1783c63b
commit a4f9c63288
235 changed files with 974 additions and 974 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -8,7 +8,7 @@ description: >-
# JSON Configuration Syntax
Most OpenTF configurations are written in
[the native OpenTF language syntax](/opentf/language/syntax/configuration), which is designed to be
[the native OpenTF language syntax](/docs/language/syntax/configuration), which is designed to be
relatively easy for humans to read and update.
OpenTF also supports an alternative syntax that is JSON-compatible. This
@@ -92,7 +92,7 @@ different (see the [block-type-specific exceptions](#block-type-specific-excepti
correspond either to argument names or to nested block type names.
* Where a property corresponds to an argument that accepts
[arbitrary expressions](/opentf/language/expressions) in the native syntax, the
[arbitrary expressions](/docs/language/expressions) in the native syntax, the
property value is mapped to an expression as described under
[_Expression Mapping_](#expression-mapping) below. For arguments that
do _not_ accept arbitrary expressions, the interpretation of the property
@@ -109,7 +109,7 @@ different (see the [block-type-specific exceptions](#block-type-specific-excepti
## Expression Mapping
Since JSON grammar is not able to represent all of the OpenTF language
[expression syntax](/opentf/language/expressions), JSON values interpreted as expressions
[expression syntax](/docs/language/expressions), JSON values interpreted as expressions
are mapped as follows:
| JSON | OpenTF Language Interpretation |