changesets: changesets for new events backend bus
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
This commit is contained in:
@@ -0,0 +1,9 @@
|
||||
---
|
||||
'@backstage/plugin-events-backend': patch
|
||||
---
|
||||
|
||||
The events backend now has its own built-in event bus for distributing events across multiple backend instances. It exposes a new HTTP API under `/bus/v1/` for publishing and reading events from the bus, as well as its own storage and notification mechanism for events.
|
||||
|
||||
The backing event store for the bus only supports scaled deployment if PostgreSQL is used as the DBMS. If SQLite or MySQL is used, the event bus will fall back to an in-memory store that does not support multiple backend instances.
|
||||
|
||||
The default `EventsService` implementation from `@backstage/plugin-events-node` has also been updated to use the new events bus.
|
||||
@@ -2,4 +2,4 @@
|
||||
'@backstage/plugin-events-node': patch
|
||||
---
|
||||
|
||||
The `EventParams` payload must now be a `JsonValue`, and the `metadata` type has been tweaked.
|
||||
The default implementation of the `EventsService` now uses the new event bus for distributing events across multiple backend instances if the events backend plugin is installed.
|
||||
|
||||
Reference in New Issue
Block a user