open-telemetry / open-telemetry/opentelemetry-python
config: Review config env var resolution to configmap
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
LGTM.
By the way, it might be worth looking at: https://github.com/open-telemetry/opentelemetry-collector/tree/main/confmap
I'm not sure if declarative config is thinking of adding custom resolvers, but currently the collector does inside-out resolution to allow for things like:
${secretsmanager:${env:NEWRELIC_OTLP_ENDPOINT}}
Originally posted by @herin049 in https://github.com/open-telemetry/opentelemetry-python/issues/5091#issuecomment-4248561214
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the confmap directory linked in the issue and the declarative-config resolution code; compare its behavior with the nested example shown. Done means the scope for custom resolvers and configmap resolution has been decided and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100