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: schemas/README.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,8 @@ Optional field set attributes:
32
32
- type (ignored): at this level, should always be `group`
33
33
- reusable (optional): Used to identify which field sets are expected to be reused in multiple places.
34
34
See "Field set reuse" for details.
35
+
- beta: Adds a beta marker for the entire fieldset. The text provided in this attribute is used as content of the beta marker in the documentation.
36
+
Beta notices should not have newlines.
35
37
36
38
### Field set reuse
37
39
@@ -104,6 +106,18 @@ The above defines all process fields in both places:
104
106
}
105
107
```
106
108
109
+
The `beta` marker can optionally be used along with `at` and `as` to include a beta marker in the field reuses section, marking specific reuse locations as beta.
110
+
Beta notices should not have newlines.
111
+
112
+
```
113
+
reusable:
114
+
top_level: true
115
+
expected:
116
+
- at: user
117
+
as: target
118
+
beta: Reusing these fields in this location is currently considered beta.
119
+
```
120
+
107
121
### List of fields
108
122
109
123
Array of YAML objects:
@@ -134,6 +148,7 @@ Supported keys to describe fields
134
148
- format: Field format that can be used in a Kibana index template.
135
149
- normalize: Normalization steps that should be applied at ingestion time. Supported values:
136
150
- array: the content of the field should be an array (even when there's only one value).
151
+
- beta (optional): Adds a beta marker for the field to the description. The text provided in this attribute is used as content of the beta marker in the documentation. Note that when a whole field set is marked as beta, it is not necessary nor recommended to mark all fields in the field set as beta. Beta notices should not have newlines.
137
152
138
153
Supported keys to describe expected values for a field
0 commit comments