-
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
[otelcol] Remove all default providers/converters #10436
[otelcol] Remove all default providers/converters #10436
Conversation
3053801
to
99dfa08
Compare
99dfa08
to
ce55ff2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we file an issue on the Jaeger project and ping Yuri there so that they are aware of this change?
I'm planning to submit another PR to jaeger to handle the deprecation process, was waiting for the 0.103.0 release to finish in Contrib. I've already update Jaeger to pass in providers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there are some tests to fix, but otherwise this LGTM. I would like to merge this after Jaeger is fixed
Jaeger is updated: jaegertracing/jaeger#5657 |
@@ -258,6 +258,8 @@ func TestGenerateAndCompile(t *testing.T) { | |||
testCase: "Default Configuration Compilation", | |||
cfgBuilder: func(t *testing.T) Config { | |||
cfg := newTestConfig() | |||
err := cfg.SetBackwardsCompatibility() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These tests all pass in a list of providers, and therefore depend on those providers in the go mod list. The builder templates only add them when .Distribution.SupportsConfmapFactories
is true. That value was not being set so all these tests should have been failing. They were saved instead by the fact that otelcol depended on the providers. The changes in this PR remove those dependencies when otelcoltest
is not being used, so these tests started failing. The fix was to make sure .Distribution.SupportsConfmapFactories
is true, which is included in cfg.SetBackwardsCompatibility()
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch, thanks for the explanation.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #10436 +/- ##
==========================================
- Coverage 92.40% 92.40% -0.01%
==========================================
Files 393 393
Lines 18584 18567 -17
==========================================
- Hits 17173 17156 -17
Misses 1056 1056
Partials 355 355 ☔ View full report in Codecov by Sentry. |
@TylerHelmuth can you resolve the conflict? |
@mx-psi conflict handled. |
@evan-bradley will merge this by Friday EU morning unless you comment by then! |
Sorry, I was out last week, thanks for not holding this up on me. This looks good to me, the negative diff in the go.mod file is a win in my eyes. |
Agreed, I am pretty happy about the |
Description
Removed deprecated
NewCommand
. DeprecatesNewCommandMustSetProvider
. AddsNewCommand
that requires at least one provider be set.Removes usage of imported providers/converters from otelcol (but they still live in otelcoltest until #10417 is merged.
Link to tracking issue
closes #10290.
Testing
Unit tests