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
[mdatagen] Replace attributes optional field with requirement_level
metadata.yaml schema change for attributes: boolean `optional` field replaced with enum `requirement_level` field with the following options:
- `required`: attribute is always included and cannot be excluded
- `conditionally_required`: attribute is included by default when certain conditions are met (replaces `optional: true`)
- `recommended`: attribute is included by default but can be disabled via configuration (replaces `optional: false`)
- `opt_in`: attribute is not included unless explicitly enabled in user config
The `recommended` option is assumed when requirement_level isn't specified explicitly which is the case for the vast majority use cases.
metadata.yaml files upgrade guideline: Replace `optional: true` with `requirement_level: conditionally_required` and `optional: false` with `requirement_level: recommended` (or omit for default) in metadata files.
8b0990
# Use this changelog template to create an entry for release notes.
2
+
3
+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4
+
change_type: breaking
5
+
6
+
# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
7
+
component: mdatagen
8
+
9
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10
+
note: "Replace `optional` field with `requirement_level` field for attributes in metadata schema"
11
+
12
+
# One or more tracking issues or pull requests related to the change
13
+
issues: [13913]
14
+
15
+
# (Optional) One or more lines of additional information to render under the primary note.
16
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17
+
# Use pipe (|) for multiline entries.
18
+
subtext: |
19
+
The `optional` boolean field for attributes has been replaced with a `requirement_level` field that accepts enum values: `required`, `conditionally_required`, `recommended`, or `opt_in`.
20
+
- `required`: attribute is always included and cannot be excluded
21
+
- `conditionally_required`: attribute is included by default when certain conditions are met (replaces `optional: true`)
22
+
- `recommended`: attribute is included by default but can be disabled via configuration (replaces `optional: false`)
23
+
- `opt_in`: attribute is not included unless explicitly enabled in user config
24
+
When `requirement_level` is not specified, it defaults to `recommended`.
25
+
26
+
# Optional: The change log or logs in which this entry should be included.
27
+
# e.g. '[user]' or '[user, api]'
28
+
# Include 'user' if the change is relevant to end users.
29
+
# Include 'api' if there is a change to a library API.
0 commit comments