Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/adrianriobo/qe-eventmanager
Event handler to integrate corporate messaging mechanism with CI/CD
https://github.com/adrianriobo/qe-eventmanager
amqp ci-cd github-api messaging openshift-v4 tekton-pipelines
Last synced: about 2 months ago
JSON representation
Event handler to integrate corporate messaging mechanism with CI/CD
- Host: GitHub
- URL: https://github.com/adrianriobo/qe-eventmanager
- Owner: adrianriobo
- Created: 2021-04-21T13:10:19.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-10-23T19:24:27.000Z (2 months ago)
- Last Synced: 2024-10-24T05:59:28.313Z (2 months ago)
- Topics: amqp, ci-cd, github-api, messaging, openshift-v4, tekton-pipelines
- Language: Go
- Homepage:
- Size: 9.9 MB
- Stars: 8
- Watchers: 2
- Forks: 1
- Open Issues: 30
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# qe-eventmanager
[](https://quay.io/repository/ariobolo/qe-eventmanager)
## Roles
The app can act as a manager handling integrations based on flow definitions, or it can act as a tool to interact within the providers configured.
### Actioner
As an actioner the cli allows to run single actions:
* Send an UMB menssage
```bash
./qe-eventmanager umb send -p providers.yaml \
-m message.json \
-d VirtualTopic.sample
```
* Create / update a repository status on github
```bash
./qe-eventmanager github status -p providers.yaml \
-s success \
-o sample-owner \
--repo sample-repo \
--ref SHA_COMMIT
```
### Manager
As a manager integrate providers based on flow definitnions:
```bash
./qe-eventmanager start -p providers.yaml \
-f flow1.yaml,flow2.yaml
```
A simple overview on an umb-tekton integration
## Configuration
The eventmanager requires a set of information around the `providers` on which it can act upon
and a set or `flows` defining the integrations and the actions to be executed.
### Providers
```yaml
umb:
consumerID: foo
driver: amqp
brokers: broker1:5556,broker2:5556
userCertificate: XXXXXXX # encoded as base64
userKey: XXXXX # encoded as base64
certificateAuthority: XXXXXX # encoded as base64
tekton:
namespace: myNamespace
workspaces:
- name: workspace1
pvc: pvc1
- name: workspace2
pvc: pvc2
kubeconfig: XXXXXX # encoded as base64. This value is optional is used to connect to remote cluster
# Otherwise eventmanager can rely on RBAC when running inside the cluster
github: # Can be configured to auth based on pat or as a github app, bot require read public repos and read-write status rights
token: github_pat_token
appID: 1
appInstallationID: 99
appKey: XXXXXX # encoded as base64
```
### Flows
```yaml
name: sample-flow
input:
umb:
topic: topic-to-consume
filters:
- $.node1.node2[?(@.field1=='value1')].field1
- $.node1.node2[?(@.field2=='value2')].field1
ack:
github:
status:
ref: $.node1.node2.sha
owner: sample-owner
repo: sample-repo # Configured github providers require rights on this repo
status: pending
action:
tektonPipeline:
name: XXX
params:
- name: foo
value: $.node1.node2[(@.field=='foo')].id # $. jsonpath expression function
- name: bar
value: bar # constant string
success:
umb:
topic: topic-to-produce
eventSchema: message-schema-to-send
eventFields:
- name: foo
value: $(pipeline.results.result1) # Pick value from pipeline results result1
- name: bar
value: bar # constant string
error:
github:
status:
ref: $.node1.node2.sha
owner: sample-owner
repo: sample-repo # Configured github providers require rights on this repo
status: error
```
## Build
### Cli
```bash
make clean
make build
```
### Container
```bash
make container-build
```