Add an event router for Gerrit
which handles events from the topic `gerrit`
and re-publishes events under their more specific topic
based on the `$.type` payload field
like e.g., `gerrit.change-merged`.
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
Add an event router for Azure DevOps
which handles events from the topic `azureDevOps`
and re-publishes events under their more specific topic
based on the `$.eventType` payload field
like e.g., `azureDevOps.git.push`.
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
Add an event router for GitLab
which handles events from the topic `gitlab`
and re-publishes events under their more specific topic
based on the `$.event_name` payload field
like e.g., `gitlab.push`.
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
Add an event router for GitHub
which handles events from the topic `github`
and re-publishes events under their more specific topic
based on the `x-github-event` metadata
like e.g., `github.push`.
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
Add an event router for Bitbucket Cloud
which handles events from the topic `bitbucketCloud`
and re-publishes events under their more specific topic
based on the `x-event-key` metadata
like e.g., `bitbucketCloud.repo:push`.
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
This change introduces a new plugin `@backstage/plugin-events-backend-module-aws-sqs`.
This plugin provides an event publisher which receives events from
(an) AWS SQS queue(s) and publishes them to the event broker.
The plugin supports the new backend-plugin-api and connects with the other plugins.
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
This plugin adds an event publisher which receives events via (an) HTTP endpoint(s)
and can be used as destination at webhook subscriptions.
Relates-to: #11082
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
This change introduces some new plugins which provide the basics
for managing events inside of backstage.
Hereby, it offers extension points to add event publishers and subscribers
as well as to exchange the event broker implementation.
- `@backstage/plugin-events-backend`:
backend for the events management which connects all parts
and provides a simple in-memory event broker
- `@backstage/plugin-events-node`:
interfaces and API for `@backstage/plugin-events-backend`
- `@backstage/plugin-events-test-utils`:
test utilities like implementations useful for writing tests at modules
All plugins support the new backend-plugin-api.
Relates-to: #11082
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
Currently, all configuration options for the `CatalogGraphCard` are lost
at the "View Graph" link at the bottom which opens the full graph view
using the current entity as root entity.
Esp. for `maxDepth` the default was Infinite / no limit.
The change will preserve options used at the `CatalogGraphCard`
(displayed at the entity page) and additionally, increments the
`maxDepth` option by 1 to increase the scope slightly compared to
the graph already seen by the users.
The default for `maxDepth` at `CatalogGraphCard` is 1.
Closes: #14462
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
Use the routing key if it's available instead of team name when triggering incidents.
BREAKING CHANGE:
Before, the team name was used even if the routing key (with or without team) was used.
Now, the routing key defined for the component will be used instead of the team name.
Closes: #14453
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
Patrick Jungermann