It appears that further items have been added to out-of-the-box .dockerignore file created when running `@backstage/create-app`
Updated to reflect the current contents
was:
```
.git
node_modules
packages/*/src
packages/*/node_modules
plugins
```
now:
```
.git
.yarn/cache
.yarn/install-state.gz
node_modules
packages/*/src
packages/*/node_modules
plugins
*.local.yaml
```
Signed-off-by: Leena <19555355+sploschee@users.noreply.github.com>
This creates a new configuration parameter `jwtHeader` for the gcp-iap
auth provider. This allows setting a custom header to look in for the
IAP issued JWT.
Signed-off-by: Adam Kunicki <kunickiaj@gmail.com>
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>
Integrate plugins-events-backend with plugins-events-backend-module-http
at the example backend.
Relates-to: #11082
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>
Patrik Oldsberg