Tyler Helmuth

Spent some time on this today and ran into this problem: https://github.com/orgs/goreleaser/discussions/4469. A workaround would be to use multiple goreleaser configuration files, but I'd like to avoid that if possible.

@jpkrohling looking at your repo I do like how there are individual gorelease configs. This will be really useful for certain distributions, like k8s or sidecar, that don't need to...

I was wrong, we can still generate the files like you do in your repo.

@jpkrohling here is a PR for what the generated files can look like: https://github.com/open-telemetry/opentelemetry-collector-releases/pull/486. I think the auto-generated files will break down if we ever make any specific distributions, like...

We now have a CI process that separates the builds!

With https://github.com/open-telemetry/opentelemetry-collector/pull/10413 merged, the decision to keep `Start` returning an error is [solidified](https://github.com/open-telemetry/opentelemetry-collector/blame/dadc331464a5f3e606d58b73aaf1f88e82c48c9c/docs/rfcs/component-status-reporting.md#L93).

Agreed

We took a shot at this via https://github.com/open-telemetry/opentelemetry-collector/pull/9996, but ultimately could not get consensus from approvers and maintainers on accepting the change. Ultimately, I think @jpkrohling summed up the feelings...

@mx-psi with the new error logs for `$ENV` and the ongoing work to move `$ENV` expansion behind a feature gate with eventual plans of deprecation I feel we can move...

With a plausible implementation example via https://github.com/open-telemetry/opentelemetry-collector/pull/10947, I'd like to take a vote on whether @open-telemetry/collector-contrib-approvers @open-telemetry/collector-approvers view this change as valueable. Benefits of the change: - Cleaner code to...