- Updated dependencies
- @backstage/backend-common@0.22.0-next.1
- @backstage/plugin-events-node@0.3.4-next.1
- @backstage/backend-plugin-api@0.6.18-next.1
- Updated dependencies
- @backstage/backend-common@0.21.8-next.0
- @backstage/backend-plugin-api@0.6.18-next.0
- @backstage/config@1.2.0
- @backstage/plugin-events-node@0.3.4-next.0
- 7899e55: Allow unauthenticated requests for HTTP ingress.
- Updated dependencies
- @backstage/backend-common@0.21.7
- @backstage/backend-plugin-api@0.6.17
- @backstage/plugin-events-node@0.3.3
- @backstage/config@1.2.0
- 7899e55: Allow unauthenticated requests for HTTP ingress.
- Updated dependencies
- @backstage/backend-common@0.21.7-next.1
- @backstage/backend-plugin-api@0.6.17-next.1
- @backstage/plugin-events-node@0.3.3-next.1
- @backstage/config@1.2.0
- Updated dependencies
- @backstage/backend-common@0.21.7-next.0
- @backstage/backend-plugin-api@0.6.17-next.0
- @backstage/config@1.2.0
- @backstage/plugin-events-node@0.3.3-next.0
- Updated dependencies
- @backstage/backend-common@0.21.6
- @backstage/backend-plugin-api@0.6.16
- @backstage/plugin-events-node@0.3.2
- @backstage/config@1.2.0
- Updated dependencies
- @backstage/backend-common@0.21.5
- @backstage/plugin-events-node@0.3.1
- @backstage/backend-plugin-api@0.6.15
- @backstage/config@1.2.0
-
c4bd794: BREAKING CHANGE: Migrate
HttpPostIngressEventPublisher
andeventsPlugin
to useEventsService
.Uses the
EventsService
instead ofEventBroker
atHttpPostIngressEventPublisher
, dropping the use ofEventPublisher
includingsetEventBroker(..)
.Now,
HttpPostIngressEventPublisher.fromConfig
requiresevents: EventsService
as option.const http = HttpPostIngressEventPublisher.fromConfig({ config: env.config, + events: env.events, logger: env.logger, }); http.bind(eventsRouter); // e.g. at packages/backend/src/plugins/events.ts - await new EventsBackend(env.logger) - .setEventBroker(env.eventBroker) - .addPublishers(http) - .start(); // or for other kinds of setups - await Promise.all(http.map(publisher => publisher.setEventBroker(eventBroker)));
eventsPlugin
uses theeventsServiceRef
as dependency. Unsupported (and deprecated) extension point methods will throw an error to prevent unintended behavior.import { eventsServiceRef } from '@backstage/plugin-events-node';
-
56969b6: Add new
EventsService
as well aseventsServiceRef
for the new backend system.Summary:
- new:
EventsService
,eventsServiceRef
,TestEventsService
- deprecated:
EventBroker
,EventPublisher
,EventSubscriber
,DefaultEventBroker
,EventsBackend
, most parts ofEventsExtensionPoint
(alpha),TestEventBroker
,TestEventPublisher
,TestEventSubscriber
Add the
eventsServiceRef
as dependency to your backend plugins or backend plugin modules.Details:
The previous implementation using the
EventsExtensionPoint
was added in the early stages of the new backend system and does not respect the plugin isolation. This made it not compatible anymore with the new backend system.Additionally, the previous interfaces had some room for simplification, supporting less exposure of internal concerns as well.
Hereby, this change adds a new
EventsService
interface as replacement for the now deprecatedEventBroker
. The new interface does not require anyEventPublisher
orEventSubscriber
interfaces anymore. Instead, it is expected that theEventsService
gets passed into publishers and subscribers, and used internally. There is no need to expose anything of that at their own interfaces.Most parts of
EventsExtensionPoint
(alpha) are deprecated as well and were not usable (by other plugins or their modules) anyway.The
DefaultEventBroker
implementation is deprecated and wraps the newDefaultEventsService
implementation. Optionally, an instance can be passed as argument to allow mixed setups to operate alongside. - new:
-
Updated dependencies
- @backstage/plugin-events-node@0.3.0
- @backstage/backend-common@0.21.4
- @backstage/config@1.2.0
- @backstage/backend-plugin-api@0.6.14
- Updated dependencies
- @backstage/backend-common@0.21.4-next.2
- @backstage/backend-plugin-api@0.6.14-next.2
- @backstage/config@1.2.0-next.1
- @backstage/plugin-events-node@0.3.0-next.2
- Updated dependencies
- @backstage/config@1.2.0-next.1
- @backstage/backend-common@0.21.4-next.1
- @backstage/backend-plugin-api@0.6.14-next.1
- @backstage/plugin-events-node@0.3.0-next.1
-
c4bd794: BREAKING CHANGE: Migrate
HttpPostIngressEventPublisher
andeventsPlugin
to useEventsService
.Uses the
EventsService
instead ofEventBroker
atHttpPostIngressEventPublisher
, dropping the use ofEventPublisher
includingsetEventBroker(..)
.Now,
HttpPostIngressEventPublisher.fromConfig
requiresevents: EventsService
as option.const http = HttpPostIngressEventPublisher.fromConfig({ config: env.config, + events: env.events, logger: env.logger, }); http.bind(eventsRouter); // e.g. at packages/backend/src/plugins/events.ts - await new EventsBackend(env.logger) - .setEventBroker(env.eventBroker) - .addPublishers(http) - .start(); // or for other kinds of setups - await Promise.all(http.map(publisher => publisher.setEventBroker(eventBroker)));
eventsPlugin
uses theeventsServiceRef
as dependency. Unsupported (and deprecated) extension point methods will throw an error to prevent unintended behavior.import { eventsServiceRef } from '@backstage/plugin-events-node';
-
56969b6: Add new
EventsService
as well aseventsServiceRef
for the new backend system.Summary:
- new:
EventsService
,eventsServiceRef
,TestEventsService
- deprecated:
EventBroker
,EventPublisher
,EventSubscriber
,DefaultEventBroker
,EventsBackend
, most parts ofEventsExtensionPoint
(alpha),TestEventBroker
,TestEventPublisher
,TestEventSubscriber
Add the
eventsServiceRef
as dependency to your backend plugins or backend plugin modules.Details:
The previous implementation using the
EventsExtensionPoint
was added in the early stages of the new backend system and does not respect the plugin isolation. This made it not compatible anymore with the new backend system.Additionally, the previous interfaces had some room for simplification, supporting less exposure of internal concerns as well.
Hereby, this change adds a new
EventsService
interface as replacement for the now deprecatedEventBroker
. The new interface does not require anyEventPublisher
orEventSubscriber
interfaces anymore. Instead, it is expected that theEventsService
gets passed into publishers and subscribers, and used internally. There is no need to expose anything of that at their own interfaces.Most parts of
EventsExtensionPoint
(alpha) are deprecated as well and were not usable (by other plugins or their modules) anyway.The
DefaultEventBroker
implementation is deprecated and wraps the newDefaultEventsService
implementation. Optionally, an instance can be passed as argument to allow mixed setups to operate alongside. - new:
-
Updated dependencies
- @backstage/plugin-events-node@0.3.0-next.0
- @backstage/backend-common@0.21.3-next.0
- @backstage/backend-plugin-api@0.6.13-next.0
- @backstage/config@1.1.2-next.0
- 9aac2b0: Use
--cwd
as the firstyarn
argument - Updated dependencies
- @backstage/backend-common@0.21.0
- @backstage/backend-plugin-api@0.6.10
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.19
- Updated dependencies
- @backstage/backend-common@0.21.0-next.3
- @backstage/backend-plugin-api@0.6.10-next.3
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.19-next.3
- 9aac2b0: Use
--cwd
as the firstyarn
argument - Updated dependencies
- @backstage/backend-common@0.21.0-next.2
- @backstage/backend-plugin-api@0.6.10-next.2
- @backstage/plugin-events-node@0.2.19-next.2
- @backstage/config@1.1.1
- Updated dependencies
- @backstage/backend-plugin-api@0.6.10-next.1
- @backstage/backend-common@0.21.0-next.1
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.19-next.1
- Updated dependencies
- @backstage/backend-common@0.21.0-next.0
- @backstage/backend-plugin-api@0.6.10-next.0
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.19-next.0
- 92ea615: Update
README.md
- d5ddc4e: Add documentation on how to install the plugins with the new backend system.
- Updated dependencies
- @backstage/backend-common@0.20.1
- @backstage/backend-plugin-api@0.6.9
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.18
- Updated dependencies
- @backstage/backend-plugin-api@0.6.9-next.2
- @backstage/backend-common@0.20.1-next.2
- @backstage/plugin-events-node@0.2.18-next.2
- Updated dependencies
- @backstage/backend-common@0.20.1-next.1
- @backstage/config@1.1.1
- @backstage/backend-plugin-api@0.6.9-next.1
- @backstage/plugin-events-node@0.2.18-next.1
- Updated dependencies
- @backstage/backend-common@0.20.1-next.0
- @backstage/backend-plugin-api@0.6.9-next.0
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.18-next.0
- cc4228e: Switched module ID to use kebab-case.
- Updated dependencies
- @backstage/backend-common@0.20.0
- @backstage/backend-plugin-api@0.6.8
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.17
- Updated dependencies
- @backstage/backend-common@0.20.0-next.3
- @backstage/backend-plugin-api@0.6.8-next.3
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.17-next.3
- cc4228e: Switched module ID to use kebab-case.
- Updated dependencies
- @backstage/backend-common@0.20.0-next.2
- @backstage/backend-plugin-api@0.6.8-next.2
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.17-next.2
- Updated dependencies
- @backstage/backend-common@0.20.0-next.1
- @backstage/backend-plugin-api@0.6.8-next.1
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.17-next.1
- Updated dependencies
- @backstage/backend-common@0.20.0-next.0
- @backstage/backend-plugin-api@0.6.8-next.0
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.17-next.0
- Updated dependencies
- @backstage/backend-common@0.19.9
- @backstage/backend-plugin-api@0.6.7
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.16
- Updated dependencies
- @backstage/backend-plugin-api@0.6.7-next.2
- @backstage/backend-common@0.19.9-next.2
- @backstage/plugin-events-node@0.2.16-next.2
- Updated dependencies
- @backstage/backend-common@0.19.9-next.1
- @backstage/backend-plugin-api@0.6.7-next.1
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.16-next.1
- Updated dependencies
- @backstage/backend-common@0.19.9-next.0
- @backstage/backend-plugin-api@0.6.7-next.0
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.16-next.0
- Updated dependencies
- @backstage/backend-common@0.19.8
- @backstage/backend-plugin-api@0.6.6
- @backstage/config@1.1.1
- @backstage/plugin-events-node@0.2.15
- Updated dependencies
- @backstage/backend-common@0.19.8-next.2
- @backstage/backend-plugin-api@0.6.6-next.2
- @backstage/config@1.1.1-next.0
- @backstage/plugin-events-node@0.2.15-next.2
- Updated dependencies
- @backstage/backend-common@0.19.7-next.1
- @backstage/backend-plugin-api@0.6.5-next.1
- @backstage/config@1.1.0
- @backstage/plugin-events-node@0.2.14-next.1
- Updated dependencies
- @backstage/backend-common@0.19.7-next.0
- @backstage/config@1.1.0
- @backstage/backend-plugin-api@0.6.5-next.0
- @backstage/plugin-events-node@0.2.14-next.0
-
71114ac50e02: The export for the new backend system has been moved to be the
default
export.For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend'; backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
-
Updated dependencies
- @backstage/backend-common@0.19.5
- @backstage/config@1.1.0
- @backstage/backend-plugin-api@0.6.3
- @backstage/plugin-events-node@0.2.12
-
71114ac50e02: The export for the new backend system has been moved to be the
default
export.For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend'; backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
-
Updated dependencies
- @backstage/config@1.1.0-next.2
- @backstage/backend-plugin-api@0.6.3-next.3
- @backstage/backend-common@0.19.5-next.3
- @backstage/plugin-events-node@0.2.12-next.3
- Updated dependencies
- @backstage/config@1.1.0-next.1
- @backstage/backend-common@0.19.5-next.2
- @backstage/backend-plugin-api@0.6.3-next.2
- @backstage/plugin-events-node@0.2.12-next.2
- Updated dependencies
- @backstage/config@1.1.0-next.0
- @backstage/backend-common@0.19.5-next.1
- @backstage/backend-plugin-api@0.6.3-next.1
- @backstage/plugin-events-node@0.2.12-next.1
- Updated dependencies
- @backstage/backend-common@0.19.4-next.0
- @backstage/backend-plugin-api@0.6.2-next.0
- @backstage/config@1.0.8
- @backstage/plugin-events-node@0.2.11-next.0
- 629cbd194a87: Use
coreServices.rootConfig
instead ofcoreService.config
- 12a8c94eda8d: Add package repository and homepage metadata
- Updated dependencies
- @backstage/backend-common@0.19.2
- @backstage/backend-plugin-api@0.6.0
- @backstage/plugin-events-node@0.2.9
- @backstage/config@1.0.8
- Updated dependencies
- @backstage/backend-plugin-api@0.6.0-next.2
- @backstage/backend-common@0.19.2-next.2
- @backstage/plugin-events-node@0.2.9-next.2
- 629cbd194a87: Use
coreServices.rootConfig
instead ofcoreService.config
- 12a8c94eda8d: Add package repository and homepage metadata
- Updated dependencies
- @backstage/backend-common@0.19.2-next.1
- @backstage/plugin-events-node@0.2.9-next.1
- @backstage/backend-plugin-api@0.6.0-next.1
- @backstage/config@1.0.8
- Updated dependencies
- @backstage/backend-common@0.19.2-next.0
- @backstage/backend-plugin-api@0.5.5-next.0
- @backstage/config@1.0.8
- @backstage/plugin-events-node@0.2.9-next.0
- Updated dependencies
- @backstage/backend-common@0.19.1
- @backstage/backend-plugin-api@0.5.4
- @backstage/config@1.0.8
- @backstage/plugin-events-node@0.2.8
- Updated dependencies
- @backstage/backend-common@0.19.1-next.0
- @backstage/backend-plugin-api@0.5.4-next.0
- @backstage/config@1.0.8
- @backstage/plugin-events-node@0.2.8-next.0
- Updated dependencies
- @backstage/backend-common@0.19.0
- @backstage/backend-plugin-api@0.5.3
- @backstage/config@1.0.8
- @backstage/plugin-events-node@0.2.7
- Updated dependencies
- @backstage/backend-common@0.19.0-next.2
- @backstage/backend-plugin-api@0.5.3-next.2
- @backstage/config@1.0.7
- @backstage/plugin-events-node@0.2.7-next.2
- Updated dependencies
- @backstage/backend-common@0.19.0-next.1
- @backstage/backend-plugin-api@0.5.3-next.1
- @backstage/plugin-events-node@0.2.7-next.1
- @backstage/config@1.0.7
- Updated dependencies
- @backstage/backend-common@0.18.6-next.0
- @backstage/config@1.0.7
- @backstage/backend-plugin-api@0.5.3-next.0
- @backstage/plugin-events-node@0.2.7-next.0
- Updated dependencies
- @backstage/backend-common@0.18.5
- @backstage/backend-plugin-api@0.5.2
- @backstage/config@1.0.7
- @backstage/plugin-events-node@0.2.6
- Updated dependencies
- @backstage/backend-common@0.18.5-next.1
- @backstage/backend-plugin-api@0.5.2-next.1
- @backstage/config@1.0.7
- @backstage/plugin-events-node@0.2.6-next.1
- Updated dependencies
- @backstage/backend-common@0.18.5-next.0
- @backstage/backend-plugin-api@0.5.2-next.0
- @backstage/config@1.0.7
- @backstage/plugin-events-node@0.2.6-next.0
-
3538d9ad2c4: Export
DefaultEventBroker
to allow decoupling of the catalog and events backends in theexample-backend
.Please look at
plugins/events-backend/README.md
for the currently advised way to set up the event backend and catalog providers. -
Updated dependencies
- @backstage/backend-common@0.18.4
- @backstage/backend-plugin-api@0.5.1
- @backstage/config@1.0.7
- @backstage/plugin-events-node@0.2.5
-
3538d9ad2c4: Export
DefaultEventBroker
to allow decoupling of the catalog and events backends in theexample-backend
.Please look at
plugins/events-backend/README.md
for the currently advised way to set up the event backend and catalog providers. -
Updated dependencies
- @backstage/backend-common@0.18.4-next.2
- @backstage/backend-plugin-api@0.5.1-next.2
- @backstage/config@1.0.7
- @backstage/plugin-events-node@0.2.5-next.2
- Updated dependencies
- @backstage/backend-common@0.18.4-next.2
- @backstage/backend-plugin-api@0.5.1-next.2
- @backstage/config@1.0.7
- @backstage/plugin-events-node@0.2.5-next.2
- Updated dependencies
- @backstage/backend-common@0.18.4-next.1
- @backstage/backend-plugin-api@0.5.1-next.1
- @backstage/config@1.0.7
- @backstage/plugin-events-node@0.2.5-next.1
- Updated dependencies
- @backstage/backend-common@0.18.4-next.0
- @backstage/config@1.0.7
- @backstage/backend-plugin-api@0.5.1-next.0
- @backstage/plugin-events-node@0.2.5-next.0
- 928a12a9b3e: Internal refactor of
/alpha
exports. - a5de745ac17: Updated README instructions
- Updated dependencies
- @backstage/backend-common@0.18.3
- @backstage/backend-plugin-api@0.5.0
- @backstage/plugin-events-node@0.2.4
- @backstage/config@1.0.7
- Updated dependencies
- @backstage/backend-common@0.18.3-next.2
- @backstage/backend-plugin-api@0.4.1-next.2
- @backstage/plugin-events-node@0.2.4-next.2
- @backstage/config@1.0.7-next.0
- Updated dependencies
- @backstage/backend-common@0.18.3-next.1
- @backstage/backend-plugin-api@0.4.1-next.1
- @backstage/config@1.0.7-next.0
- @backstage/plugin-events-node@0.2.4-next.1
- 928a12a9b3: Internal refactor of
/alpha
exports. - Updated dependencies
- @backstage/backend-plugin-api@0.4.1-next.0
- @backstage/backend-common@0.18.3-next.0
- @backstage/plugin-events-node@0.2.4-next.0
- @backstage/config@1.0.6
- 0ff03319be: Updated usage of
createBackendPlugin
. - Updated dependencies
- @backstage/backend-plugin-api@0.4.0
- @backstage/backend-common@0.18.2
- @backstage/plugin-events-node@0.2.3
- @backstage/config@1.0.6
- 0ff03319be: Updated usage of
createBackendPlugin
. - Updated dependencies
- @backstage/backend-plugin-api@0.4.0-next.2
- @backstage/backend-common@0.18.2-next.2
- @backstage/plugin-events-node@0.2.3-next.2
- @backstage/config@1.0.6
- Updated dependencies
- @backstage/backend-common@0.18.2-next.1
- @backstage/backend-plugin-api@0.3.2-next.1
- @backstage/config@1.0.6
- @backstage/plugin-events-node@0.2.3-next.1
- Updated dependencies
- @backstage/backend-common@0.18.2-next.0
- @backstage/backend-plugin-api@0.3.2-next.0
- @backstage/plugin-events-node@0.2.3-next.0
- 217149ae98: The default event broker will now catch and log errors thrown by the
onEvent
method of subscribers. The returned promise frompublish
method will also not resolve until all subscribers have handled the event. - 8e06f3cf00: Switched imports of
loggerToWinstonLogger
to@backstage/backend-common
. - Updated dependencies
- @backstage/backend-plugin-api@0.3.0
- @backstage/backend-common@0.18.0
- @backstage/config@1.0.6
- @backstage/plugin-events-node@0.2.1
- 8e06f3cf00: Switched imports of
loggerToWinstonLogger
to@backstage/backend-common
. - Updated dependencies
- @backstage/backend-plugin-api@0.3.0-next.1
- @backstage/backend-common@0.18.0-next.1
- @backstage/plugin-events-node@0.2.1-next.1
- @backstage/config@1.0.6-next.0
- 217149ae98: The default event broker will now catch and log errors thrown by the
onEvent
method of subscribers. The returned promise frompublish
method will also not resolve until all subscribers have handled the event. - Updated dependencies
- @backstage/backend-plugin-api@0.2.1-next.0
- @backstage/backend-common@0.18.0-next.0
- @backstage/config@1.0.6-next.0
- @backstage/plugin-events-node@0.2.1-next.0
-
cf41eedf43: BREAKING: Remove required field
router
atHttpPostIngressEventPublisher.fromConfig
and replace it withbind(router: Router)
. Additionally, the path prefix/http
will be added insideHttpPostIngressEventPublisher
.// at packages/backend/src/plugins/events.ts const eventsRouter = Router(); - const httpRouter = Router(); - eventsRouter.use('/http', httpRouter); const http = HttpPostIngressEventPublisher.fromConfig({ config: env.config, logger: env.logger, - router: httpRouter, }); + http.bind(eventsRouter);
-
884d749b14: Refactored to use
coreServices
from@backstage/backend-plugin-api
. -
cf41eedf43: Introduce a new interface
RequestDetails
to abstractRequest
providing access to request body and headers.BREAKING: Replace
request: Request
withrequest: RequestDetails
atRequestValidator
. -
Updated dependencies
- @backstage/backend-common@0.17.0
- @backstage/backend-plugin-api@0.2.0
- @backstage/plugin-events-node@0.2.0
- @backstage/config@1.0.5
- Updated dependencies
- @backstage/backend-common@0.17.0-next.3
- @backstage/backend-plugin-api@0.2.0-next.3
- @backstage/config@1.0.5-next.1
- @backstage/plugin-events-node@0.2.0-next.3
- 884d749b14: Refactored to use
coreServices
from@backstage/backend-plugin-api
. - Updated dependencies
- @backstage/backend-common@0.17.0-next.2
- @backstage/backend-plugin-api@0.2.0-next.2
- @backstage/config@1.0.5-next.1
- @backstage/plugin-events-node@0.2.0-next.2
- Updated dependencies
- @backstage/backend-common@0.17.0-next.1
- @backstage/backend-plugin-api@0.1.5-next.1
- @backstage/config@1.0.5-next.1
- @backstage/plugin-events-node@0.2.0-next.1
-
cf41eedf43: BREAKING: Remove required field
router
atHttpPostIngressEventPublisher.fromConfig
and replace it withbind(router: Router)
. Additionally, the path prefix/http
will be added insideHttpPostIngressEventPublisher
.// at packages/backend/src/plugins/events.ts const eventsRouter = Router(); - const httpRouter = Router(); - eventsRouter.use('/http', httpRouter); const http = HttpPostIngressEventPublisher.fromConfig({ config: env.config, logger: env.logger, - router: httpRouter, }); + http.bind(eventsRouter);
-
cf41eedf43: Introduce a new interface
RequestDetails
to abstractRequest
providing access to request body and headers.BREAKING: Replace
request: Request
withrequest: RequestDetails
atRequestValidator
. -
Updated dependencies
- @backstage/plugin-events-node@0.2.0-next.0
- @backstage/backend-common@0.16.1-next.0
- @backstage/backend-plugin-api@0.1.5-next.0
- @backstage/config@1.0.5-next.0
-
dc9da28abd: Support events received via HTTP endpoints at plugin-events-backend.
The plugin provides an event publisher
HttpPostIngressEventPublisher
which will allow you to receive events via HTTP endpointsPOST /api/events/http/{topic}
and will publish these to the used event broker.Using a provided custom validator, you can participate in the decision which events are accepted, e.g. by verifying the source of the request.
Please find more information at https://github.com/backstage/backstage/tree/master/plugins/events-backend/README.md.
-
7bbd2403a1: Adds a new backend plugin plugin-events-backend for managing events.
plugin-events-node exposes interfaces which can be used by modules.
plugin-events-backend-test-utils provides utilities which can be used while writing tests e.g. for modules.
Please find more information at https://github.com/backstage/backstage/tree/master/plugins/events-backend/README.md.
- Updated dependencies
- @backstage/backend-common@0.16.0
- @backstage/plugin-events-node@0.1.0
- @backstage/backend-plugin-api@0.1.4
- @backstage/config@1.0.4