Marc Alff

> Up till now, we use `kitchen-sink.yaml` as a blunt instrument to: > > * Demonstrate the full configuration surface area of the schema > > * Validate that the...

Assuming something like: ``` vendor: splunk: realm: some-realm access_token: some-token ``` What is the SDK implementation of declarative configuration supposed to do with this information ? The SDK parses the...

> The SDK itself should provide access to this node. This is precisely my question, what are implementors of file configuration supposed to do here ? If an exporter is...

> [@marcalff](https://github.com/marcalff) – you are absolutely right regarding custom components (like exporters) that are instantiated when the SDK is initialized. However, there are some additional scenarios. > > In my...

@robsunday Sorry I notice your comments only today. So, if I understand correctly: * the config.yaml file is now used to represent: * (a) all the configuration data, following a...

@robsunday @ysolomchenko Thanks for the clarifications. I think I now understand better the proposal, so this is great progress. Now, I am curious about this: Instead of (1) embedding a...

> Since there is a possibility for extensions in other places, this means that if we split the file, we’ll face a situation where part of the vendor-specific configuration is...

@jack-berg Could you check your demo branch ? I can't see the script or the generated markdown. Thanks.

> Oops looks like I had some copy paste errors on the links. Fixed. > > This still needs a decent amount of work before its ready for PR, but...

@codeboten @jack-berg Any news on this ? opentelemetry-cpp is about to complete the declarative configuration implementation, and I really would like a place to report details, node by node, in...