#689 Support alternate messaging systems
Closed: Fixed 6 years ago Opened 6 years ago by mikeb.

While fedmsg can support a number of different message protocols, including AMQP and STOMP, MBS essentially hard-codes the message formats. This makes it difficult to interoperate with other messaging systems. To fix this, the MBS backend should have a declarative method of mapping message content to fields in the internal message abstraction classes. The frontend also needs to get connection information from the fedmsg config for sending individual messages.


Metadata Update from @mikeb:
- Issue assigned to mikeb

6 years ago

This was addressed by #703 which enables pluggable messaging backends.

Metadata Update from @mikeb:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata