You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 21, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+29-4Lines changed: 29 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,7 @@ Usage:
17
17
Available Commands:
18
18
help Help about any command
19
19
http update repositories in response to image hooks
20
+
pubsub update repositories in response to gcr pubsub events
20
21
update update a repository configuration
21
22
22
23
Flags:
@@ -25,9 +26,9 @@ Flags:
25
26
Use "image-updater [command] --help"for more information about a command.
26
27
```
27
28
28
-
There are two sub-commands, `http` and `update`.
29
+
There are three sub-commands, `http`, `pubsub` and `update`.
29
30
30
-
`http` provides a Webhook service, and `update` will perform the same
31
+
`http` provides a Webhook service, `pubsub` subscribes to pubsub events and `update` will perform the same
31
32
functionality from the command-line.
32
33
33
34
## Update tool
@@ -57,15 +58,22 @@ This is a micro-service for updating Git Repos when a hook is received indicatin
57
58
58
59
This currently supports receiving hooks from Docker and Quay.io.
59
60
60
-
## WARNING
61
+
###WARNING
61
62
62
63
Neither Docker Hub nor Quay.io provide a way for receivers to authenticate Webhooks, which makes this insecure, a malicious user could trigger the creation of pull requests in your git hosting service.
63
64
64
65
Please understand the risks of using this component.
65
66
67
+
## Pubsub Service
68
+
Similarly to the Webhook service, the pubsub services allows to update Git Repos when a pubsub Event is received.
69
+
70
+
This currently supports Events from [Google Cloud Registry](https://cloud.google.com/container-registry/docs/configuring-notifications).
71
+
72
+
It requires two arguments `--project-id` and `--subscription-name`. See [below](#google-container-registry-setup) for more details on how to setup the subscription.
73
+
66
74
## Configuration
67
75
68
-
This service uses a really simple configuration:
76
+
Both the Webhook and Pubsub service uses a really simple configuration:
69
77
70
78
```yaml
71
79
repositories:
@@ -133,6 +141,7 @@ changed to support Quay.io.
133
141
The `--parser` command-line option chooses which of the supported (Quay, Docker)
134
142
hook formats to parse.
135
143
144
+
136
145
## Exposing the Handler
137
146
138
147
The Service exposes a Hook handler at `/` on port 8080 that handles the
@@ -143,6 +152,22 @@ configured hook type.
143
152
A Tekton task is provided in [./tekton](./tekton) which allows you to apply
0 commit comments