[confmap] Stabilize confmap validation facilities#15142
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #15142 +/- ##
==========================================
- Coverage 91.24% 91.23% -0.02%
==========================================
Files 701 703 +2
Lines 45898 45902 +4
==========================================
- Hits 41879 41878 -1
- Misses 2816 2820 +4
- Partials 1203 1204 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Could we share this on #otel-collector-dev and the next Collector meeting? |
|
I'll merge this on or after 2026-04-29 unless there are blocking comments |
|
Discussed at 22-April-2026 SIG call, no concerns raised |
|
@evan-bradley please resolve and we can merge 👍🏻 |
Merging this PR will improve performance by 50.88%
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ⚡ | BenchmarkGRPCLogsSequential |
6.4 ms | 4.2 ms | +50.88% |
| ⚡ | BenchmarkHTTPProtoLogsSequential |
5.2 ms | 3.6 ms | +44.75% |
Comparing evan-bradley:stabilize-validator (4af90dd) with main (56e1235)
Footnotes
-
76 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
d90154d
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description The `xconfmap.Validator` interface has existed in some form for a very long time now and is ready to be stabilized. Similarly, the `xconfmap.Validate` method has existed in it's current state for over a year and doesn't have any open issues I'm aware of. It should also be ready for stabilization. Many modules depend on `xconfmap` merely for the validation facilities (as can be seen by the go.mod diffs), so this will allow them to depend on only stable modules. --------- Co-authored-by: Alex Boten <[email protected]>
Description
The
xconfmap.Validatorinterface has existed in some form for a very long time now and is ready to be stabilized. Similarly, thexconfmap.Validatemethod has existed in it's current state for over a year and doesn't have any open issues I'm aware of. It should also be ready for stabilization.Many modules depend on
xconfmapmerely for the validation facilities (as can be seen by the go.mod diffs), so this will allow them to depend on only stable modules.