Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RabbitMQ Messages should have some cloud event property fields populated, e.g. message id and correlation id #3650

Closed
abossard opened this issue Jan 16, 2025 · 2 comments · May be fixed by #3661
Closed

RabbitMQ Messages should have some cloud event property fields populated, e.g. message id and correlation id #3650

abossard opened this issue Jan 16, 2025 · 2 comments · May be fixed by #3661
Labels
kind/enhancement New feature or request stale

Comments

@abossard
Copy link
Contributor

abossard commented Jan 16, 2025 •
edited
Loading

Describe the feature

For our use case, we have a lot of downstream systems that are based on RabbitMQ and rely on message id and correlation id to be populated. These properties should be in the Cloud Event Message.

It should be applied in the PubSub as well as in the Bindings for RabbitMQ and be added to outgoing messages.

Goal

RabbitMQ messages that are being sent from PubSub or Bindings need to have the Message ID and Correlation ID from the Cloud Event Message.

Unclear

  • It's not clear to me, how e.g. the CloudEvent properties will be available in the PublishRequest type.
  • maybe it would be beneficial if the metadata of the PublishRequest can be used to set any kind of header or property in the AMQP message, so that it also works in situation, where the downstream AMQP brokers expect certain properties to be set.

Release Note

RELEASE NOTE: ADD RabbitMQ message headers and properties are populated from the CloudEvent Message
@abossard abossard added the kind/enhancement New feature or request label Jan 16, 2025
@abossard abossard changed the title Solace/AMQP Messages should habe the typical AMQP fields populated, e.g. content-type Solace/AMQP Messages should have the typical AMQP fields populated, e.g. content-type Feb 5, 2025
@abossard abossard changed the title Solace/AMQP Messages should have the typical AMQP fields populated, e.g. content-type RabbitMQ Messages should have some cloud event property fields populated, e.g. message id Feb 5, 2025
@abossard abossard changed the title RabbitMQ Messages should have some cloud event property fields populated, e.g. message id RabbitMQ Messages should have some cloud event property fields populated, e.g. message id and correlation id Feb 5, 2025
@abossard abossard mentioned this issue Feb 5, 2025
Open
3 tasks
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 7, 2025

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Mar 7, 2025
@github-actions GitHub Actions
Copy link

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement New feature or request stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for messageId, correlationId, and type in RabbitMQ bindings abossard/components-contrib
1 participant
@abossard