_propagator.py currently loads propagators by name via entry points under the opentelemetry_propagator group, but only for the composite_list (env-var style) path. The structured composite config path dispatches against a hardcoded list of known propagator types.
The OTel declarative config spec defines a PluginComponentProvider mechanism for plugin components, including propagators. Any unknown propagator name in the structured path should also be resolved via entry points, consistent with composite_list and with how other plugin components are loaded.
Related: #5053 (generic resource detector loading)
_propagator.pycurrently loads propagators by name via entry points under theopentelemetry_propagatorgroup, but only for thecomposite_list(env-var style) path. The structuredcompositeconfig path dispatches against a hardcoded list of known propagator types.The OTel declarative config spec defines a
PluginComponentProvidermechanism for plugin components, including propagators. Any unknown propagator name in the structured path should also be resolved via entry points, consistent withcomposite_listand with how other plugin components are loaded.Related: #5053 (generic resource detector loading)