Component(s)
receiver/azurefunctions
What happened?
The azurefunctionsreceiver currently has a default config that does not safely "survive" a full
config round-trip through the Collector config system.
The issue is with the auth and logs.encoding fields. The default config leaves both unset,
which is acceptable in the in-memory Go struct returned by CreateDefaultConfig(). But once that
config is marshaled and then decoded again, those empty values are interpreted as invalid component
IDs.
In practice, this shows up in generated config marshal tests as decode failures like 'auth' id must not be empty and 'logs.encoding' id must not be empty.
The default config shape becomes impossible to decode after a marshal/unmarshal cycle, even though
the original Go struct was accepted as a valid default configuration object.
Collector version
main
Environment information
No response
OpenTelemetry Collector configuration
Log output
Additional context
Found while working on open-telemetry/opentelemetry-collector#14599
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Component(s)
receiver/azurefunctions
What happened?
The
azurefunctionsreceivercurrently has a default config that does not safely "survive" a fullconfig round-trip through the Collector config system.
The issue is with the
authandlogs.encodingfields. The default config leaves both unset,which is acceptable in the in-memory Go struct returned by
CreateDefaultConfig(). But once thatconfig is marshaled and then decoded again, those empty values are interpreted as invalid component
IDs.
In practice, this shows up in generated config marshal tests as decode failures like
'auth' id must not be emptyand'logs.encoding' id must not be empty.The default config shape becomes impossible to decode after a marshal/unmarshal cycle, even though
the original Go struct was accepted as a valid default configuration object.
Collector version
main
Environment information
No response
OpenTelemetry Collector configuration
Log output
Additional context
Found while working on open-telemetry/opentelemetry-collector#14599
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.