Why does does run in this case? Or does it not matter (i.e. we only want this run once). Adding a comment here would help clarify

IMO, the new generated otlp metric files (feature_tracking_otlp.json, enabled_receivers_otlp.json) are somehow part of the Otel Collector configuration, a pre-condition for the Ops Agent otel collector to work as expected and collect self metrics about it's configuration. Considering this i made the decision to place the files in the same /run folder as the otel.yaml config :

"/run/google-cloud-ops-agent-opentelemetry-collector/otel.yaml"
"/run/google-cloud-ops-agent-opentelemetry-collector/feature_tracking_otlp.json"
"/run/google-cloud-ops-agent-opentelemetry-collector/enabled_receivers_otlp.json"

Why does does run in this case? Or does it not matter (i.e. we only want this run once). Adding a comment here would help clarify ?

It matters it only being in otel service (with the previous considerations) because :

1. The main service (service == "") does not write Config Files (it only does config validation and runs health checks). The "fluentbit" and "otel" services write the Config Files.
2. This way only "otel" service writes otel collector related config files.
3. [General Design] The systemd (and windows) services run independently. We do set preconditions for order of execution, but (as i've explored in the past) setting expectations from one service doing something before something else happens in another always potentially could create unexpected race conditions.

P.D. I tried putting everything in uc.GenerateFilesFromConfig to make everything simpler, but we need both the userConfig and the mergedConfig.

Same as before, why is this a otel specific check?

Responded in the other comment.