Add strict YAML parsing guidance to supplementary guidelines#4878
Open
zeitlinger wants to merge 3 commits intoopen-telemetry:mainfrom
Open
Add strict YAML parsing guidance to supplementary guidelines#4878zeitlinger wants to merge 3 commits intoopen-telemetry:mainfrom
zeitlinger wants to merge 3 commits intoopen-telemetry:mainfrom
Conversation
Adds a new section recommending strict YAML parsing practices for configuration files, including use of YAML 1.2 Core Schema, disabling dangerous deserialization features, and using safe parser modes. This helps prevent security issues and unintended type coercion.
jack-berg
reviewed
Feb 10, 2026
Reframe guidance toward configuration file authors instead of implementations, remove normative language (SHOULD), and add note clarifying that practices are derived from the YAML 1.2 Core Schema and common security best practices.
jack-berg
approved these changes
Feb 12, 2026
Member
|
This seems like a good addition. Adhering to strict YAML increases the likelihood of a consistent experience across languages. However, its unlikely that all language implementations can configure their YAML parsers to enforce strict parsing. And so supplementary guidance to users seems like the most appropriate way to encourage this. |
Member
Author
|
/easycla |
carlosalberto
approved these changes
Mar 3, 2026
Contributor
|
@jack-berg @zeitlinger Do we need more reviews from the config SIG? Or we good to go? |
Member
Author
|
I think we're good — two spec approver approvals should be sufficient. Thanks for the review! |
pellared
approved these changes
Mar 4, 2026
Comment on lines
+59
to
+60
| - Add strict YAML parsing guidance to configuration supplementary guidelines. | ||
| ([#4878](https://github.com/open-telemetry/opentelemetry-specification/pull/4878)) |
Member
There was a problem hiding this comment.
(nit) How about moving to "SDK Configuration" section?
reyang
approved these changes
Mar 4, 2026
seemk
approved these changes
Mar 4, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
Adds a new section recommending strict YAML parsing practices for configuration files, including use of YAML 1.2 Core Schema, disabling dangerous deserialization features, and using safe parser modes. This helps prevent security issues and unintended type coercion.
Fixes #
Changes
Please provide a brief description of the changes here.
For non-trivial changes, follow the change proposal process.
CHANGELOG.mdfile updated for non-trivial changes[chore]in the PR title to skip the changelog check