You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/develop/add-fields.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,16 +165,12 @@ Replace `String` in the field type with one of the following options:
165
165
description: |
166
166
MULTILINE_FIELD_DESCRIPTION
167
167
key_name: 'key_name'
168
-
key_description: |
169
-
MULTILINE_KEY_FIELD_DESCRIPTION
170
168
# Map of primitive values
171
169
value_type:
172
-
name: mapIntegerName
173
170
type: Integer
174
171
175
172
# Map of complex values
176
173
value_type:
177
-
name: mapObjectName
178
174
type: NestedObject
179
175
properties:
180
176
- name: 'FIELD_NAME'
@@ -185,7 +181,7 @@ Replace `String` in the field type with one of the following options:
185
181
186
182
This type is used for general-case string -> non-string type mappings, use "KeyValuePairs" for string -> string mappings. Complex maps can't be represented natively in Terraform, and this type is transformed into an associative array (TypeSet) with the key merged into the object alongside other top-level fields.
187
183
188
-
For `key_name` and `key_description`, provide a domain-appropriate name and description. For example, a map that references a specific type of resource would generally use the singular resource kind as the key name (such as "topic" for PubSub Topic) and a descriptor of the expected format depending on the context (such as resourceId vs full resource name).
184
+
For `key_name`, provide a domain-appropriate field name. For example, a map that references a specific type of resource would generally use the singular resource kind as the key name (such as "topic" for PubSub Topic).
0 commit comments