Kafka provider does not support additional message headers.

[ggallen]

Jenkins and plugins versions report

Environment

Paste the output here

What Operating System are you using (both controller, and any agents involved in the problem)?

Linux.

Reproduction steps

The Kafka provider does not support supplying additional message headers as the AMQ provider does.

Expected Results

Users can provide additional message headers.

Actual Results

Users can't provide additional message headers.

Anything else?

No response

Are you interested in contributing a fix?

No response

[lslebodn]

^^ is not clear to me whether it is about sendCIMessage step or about kafkaSubscriber in jobs dsl
because https://github.com/jenkinsci/jms-messaging-plugin?tab=readme-ov-file#retrieving-message-content says

Environment Variables
By default, the trigger and the CI Subscribe job steps save the triggering message content in an environment variable that is made available in the job. The name of this variable is configurable and defaults to "CI_MESSAGE".
Note
For the AMQ provider, the trigger will also set an environment variable named "${VARIABLE}_HEADERS" with the JSON content representing the message headers.
For the Kafka provider, the trigger will also set an environment variable named "${VARIABLE}_RECORD" with the JSON content representing the entire Kafka record.

@ggallen would you be so kind and elaborate what is the issue about?

[ggallen]

Those variables allow the user to see both the message content and the message headers.

This issue is about letting the user specify their own message headers for Kafka as they can for AMQ.