-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add entry point to build graph-based pipelines #7023
Add entry point to build graph-based pipelines #7023
Conversation
702729b
to
46be367
Compare
46be367
to
a322015
Compare
Codecov ReportBase: 90.33% // Head: 90.29% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #7023 +/- ##
==========================================
- Coverage 90.33% 90.29% -0.05%
==========================================
Files 245 245
Lines 14644 14654 +10
==========================================
+ Hits 13229 13232 +3
- Misses 1146 1152 +6
- Partials 269 270 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Please rebase |
a322015
to
7813479
Compare
Thanks, this has been rebased |
Can this be merged? |
Part of #6700
The remainder of the connectors implementation is concerned with setting up the component graph and building each node's associated component. I believe the best way to add these capabilities incrementally will be to so in a top-down way.
#6700 contains extensive testing of the graph as a whole. However, these tests interface primarily with the graph's built components. I'm not seeing a reasonable way to include coverage for a partially built graph, which I expect we would have if we follow the contribution path I've described above. My hope is that we can move forward for a few PRs based on the understanding that test coverage will be comprehensive in the end.
This PR adds the entry point to building the component graph. This entry point is hidden behind the same feature gate that was already to the
otelcol
package in #6964. However, it moves the gate to theservice
so that both packages can use it.