Spent some more time looking into this and I have questions on what the scope of this issue is. I'm new to otel, so hopefully you can give me some grace if there are obvious oversights or overly simple questions.

I can see that this repo is leveraging the "official" opentelemetry specification schema to render the generated_config.go file.

Should the Parse(config_file) function utilize this generated config for validation?
Is the purpose to ensure that all known properties from the generated config map from the input YAML to the expected structs in the generated config file, or just to focus on the environment variable handling?
If the YAML input file contains mapping unknown to the schema, how is that handled?
- The examples describing the nuance around environment variables are not part of the schema, and I also saw the "additionalProperties": true on the schema ☝️.

Any thoughts on this would be awesome, I'd be happy to help on this but if it's not high priority we can table it :)

config: Parse model from YAML #4373

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions