Documentation issue in: Building a custom collector about opentelemetry.io HOT 7 OPEN

Yes, otelcol_version should be set to 0.103.0. We had a bugfix release of the builder, but we did not release a v0.103.1 release of the rest of core modules. We likely need to update the docs automation to account for this edge case.

from opentelemetry.io.

Since this fix is likely related to infrastructure, I removed the good first issue label.

from opentelemetry.io.

Agreed that this is a pretty rare case. If the situation changes the Collector SIG and we somehow decouple builder and Collector releases we can let you know

from opentelemetry.io.

@svrnm - took a quick look. I don't think that we want any automation to handle this edge case, but rather simply (temporarily) override the version in the file in question. How does that sound @mx-psi et al? Of course we'll need to remember to remover the override if we vote for such a solution.

from opentelemetry.io.

Thanks for reporting your issue, @hyang023.

@open-telemetry/collector-approvers, could you confirm that the workaround is the right fix?

from opentelemetry.io.

Yes, otelcol_version should be set to 0.103.0. We had a bugfix release of the builder, but we did not release a v0.103.1 release of the rest of core modules. We likely need to update the docs automation to account for this edge case.

@chalin please take a look, this seems to be something where we need to update some scripts

from opentelemetry.io.

if we do a temporary fix we need a way to remind us to revert it eventually, but agreed if this is an edge case that will not happen regularly we should not automate it away

from opentelemetry.io.