Clarify declarative config default requirements #4780
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| * If a property is present and the value is null, Create MUST use the | ||
| `nullBehavior`, or `defaultBehavior` if `nullBehavior` is not set. | ||
| * If a property is required, and not present, Create MUST return an error. | ||
| * If a property is not nullable, and present and the value is null, Create MUST |
Contributor
There was a problem hiding this comment.
Minor nit: I had to read this twice to understand this bullet. Maybe there's clearer wording but I couldn't come with an improvement myself though 😓
carlosalberto
approved these changes
Dec 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the declarative config
createspec was written, declarative config was dependent on the spec as its source of truth for default values for the various properties.We now directly record expected
defaultBehaviorandnullBehaviorsemantics inopentelemetry-configuration.Updating the spec to tie things back together.
/cc @open-telemetry/configuration-approvers