Daniel Dyla

Is there any update on this?

Should I be worried the CNCF might deny this request? I hadn't expected it to take more than a week after the ticket was created in their system.

It might turn out not to matter. The branch protection rules added automatically by CNCF are actually blocking this and other use-cases. Unless we can get that resolved, we will...

So the workaround is to register a user in github, give that user permission, and generate a token to perform actions on behalf of that user. CNCF can then allowlist...

AFAIK some delay is intentional in order to allow some period for moderation if something is accidentally recorded which shouldn't be. I agree a week might be excessive though.

> JS - NPM All packages are published under the `@opentelemetry` org. There are currently 41 packages, however some small handful of them are deprecated. Would say 35+ active. @mayurkale22...

Hmm I see the issue with the logger not being constructed yet. Honestly it might be better to just fail instead of gating that behavior. The only risk is that...

nonfatalerror is probably the same thing I would have come up with if you want the fail fast strategy to be gated but I might not have used the same...

Another possible "fix" for this is to log the full collector config at startup. IIRC this is what telegraf does. This would allow the user to see that their config...

I also think a fail-fast strategy is a good one. I didn't suggest it initially because I didn't know how conservative the collector SIG tends to be about those types...