The different git notifiers need repository ids in different formats. On top of that some git providers support repositories in subgroups while others do not support nesting. Each notifier needs test to verify that they support their specific functionality. Signed-off-by: Philip Laine <philip.laine@xenit.se> |
||
|---|---|---|
| .github/workflows | ||
| api | ||
| config | ||
| controllers | ||
| docs | ||
| hack | ||
| internal | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| DCO | ||
| Dockerfile | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| PROJECT | ||
| README.md | ||
| go.mod | ||
| go.sum | ||
| main.go | ||
README.md
notification-controller
Event forwarder and notification dispatcher for the GitOps Toolkit controllers. The notification-controller is an implementation of the notification.toolkit.fluxcd.io API based on the specifications described in the RFC.
