docs/release_notes/v1.16.7.md
This update includes bug fixes:
The pubsub component did not correctly propagate tracing information when delivering messages over gRPC using raw payloads
Distributed traces were incomplete or missing links between publishers and subscribers. This prevented users from reliably correlating pubsub messages with their originating requests and spans.
The trace context from the incoming gRPC call was not correctly applied to the context used for the pubsub publish call, especially for raw payloads. As a result, the outgoing pubsub publish did not carry the expected tracing headers/metadata, so downstream components and tracing backends could not associate the published message with the originating span, leading to missing or broken traces for gRPC-based pubsub flows.
For raw payload publishes, the same trace information is now written directly into the pubsub metadata that accompanies the raw message, ensuring that tracing works consistently regardless of payload mode.
Pulsar Pubsub component oauth2ClientSecretPath configuration looked for a token and not a client secret or json credentials.
Applications using the Pulsar pubsub component with OAuth2 client credentials stored on disk via oauth2ClientSecretPath could not start successfully.
oauth2ClientSecretPath used an incorrect method NewAuthenticationTokenFromFile which looked for a token and not a client secret.
oauth2ClientSecretPath configuration is now corrected to read a client secret from file. A new option, oauth2CredentialsFile, has been added to load client_id, client_secret, issuer_url , and from a JSON file with the format: {"client_id": "...", "client_secret": "...", "issuer_url": "..."}.