[chore] add a RFC to codify the work on JSON schema configuration support #13784
Conversation
atoulme
requested review from
a team,
bogdandrutu,
codeboten,
dmitryax and
mx-psi
as code owners
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #13784 +/- ##
==========================================
+ Coverage 91.38% 92.55% +1.16%
==========================================
Files 646 656 +10
Lines 42605 36147 -6458
==========================================
- Hits 38936 33455 -5481
+ Misses 2844 1873 -971
+ Partials 825 819 -6 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
|
@jmacd I think I'd like to feel the pain of having a big schema and discuss when we get there. I am just as you can see not able to keep up with all this work and always in favor of the smallest possible step forward, knowing it doesn't scale. We can invite people to help us when we're scaling, as long as we have something that starts to work. |
3 participants
Description
Add a RFC to discuss supporting expressing the configuration of a component as a JSON schema.
Link to tracking issue
Relates to #9769 and open-telemetry/opentelemetry-collector-contrib#42214