|
2 | 2 |
|
3 | 3 | ## Modes |
4 | 4 |
|
5 | | -| **Status** | **Features** | |
6 | | -| ---------- | ------------ | |
7 | | -| working | cli | |
8 | | -| planned | web | |
9 | | -| planned | daemon | |
| 5 | +| **Status** | **Features** | |
| 6 | +| -------------- | ------------ | |
| 7 | +| ✅ Supported | cli | |
| 8 | +| 🚧 In Progress | web | |
| 9 | +| 🔜 Planned | daemon | |
10 | 10 |
|
11 | 11 | ## Sources |
12 | 12 |
|
13 | | -| Status | Features | |
14 | | -| ------- | ----------- | |
15 | | -| working | GitHub | |
16 | | -| working | Artifacthub | |
17 | | -| working | Docker Hub | |
18 | | -| planned | GitLab | |
19 | | -| planned | Bitbucket | |
20 | | -| planned | Quay | |
| 13 | +| Status | Features | |
| 14 | +| ------------ | ----------- | |
| 15 | +| ✅ Supported | GitHub | |
| 16 | +| ✅ Supported | Artifacthub | |
| 17 | +| ✅ Supported | Docker Hub | |
| 18 | +| 🔜 Planned | GitLab | |
| 19 | +| 🔜 Planned | Bitbucket | |
| 20 | +| 🔜 Planned | Quay | |
21 | 21 |
|
22 | 22 | ## Sinks |
23 | 23 |
|
24 | | -| Status | Features | |
25 | | -| ----------- | --------------- | |
26 | | -| working | Generic Webhook | |
27 | | -| working | Email | |
28 | | -| in progress | Slack | |
29 | | -| in progress | Google Chat | |
30 | | -| planned | Microsoft Teams | |
31 | | -| planned | Rocket Chat | |
| 24 | +| Status | Features | |
| 25 | +| ---------------- | --------------- | |
| 26 | +| ✅ Supported | Generic Webhook | |
| 27 | +| ✅ Supported | Email | |
| 28 | +| 🚧 Basic support | Slack | |
| 29 | +| 🚧 Basic support | Google Chat | |
| 30 | +| 🔜 Planned | Microsoft Teams | |
| 31 | +| 🔜 Planned | Rocket Chat | |
32 | 32 |
|
33 | 33 | ## Features |
34 | 34 |
|
35 | | -| Status | Features | |
36 | | -| ------- | ------------------------------------ | |
37 | | -| working | environment variables in config file | |
38 | | -| working | multiple recipients for email sink | |
| 35 | +| Status | Features | |
| 36 | +| ------------ | ------------------------------------ | |
| 37 | +| ✅ Supported | multiple notifiers for a sink | |
| 38 | +| ✅ Supported | environment variables in config file | |
| 39 | +| ✅ Supported | multiple recipients for email sink | |
39 | 40 |
|
40 | 41 | ## Ideas |
41 | 42 |
|
42 | | -| Status | Features | |
43 | | -| ------- | ------------------------------------------------------------------------------------------------------------------------- | |
44 | | -| planned | make notifiers have references to artifacts so that only one message is being sent to the sink for multiple artifacts | |
45 | | -| planned | yaml config support | |
46 | | -| planned | toml config support | |
47 | | -| planned | implement a config linter (check if notifiers, sources and references are valid) | |
48 | | -| planned | Web endpoint to silence notifications for a specific artifact | |
49 | | -| planned | update the current_version field in the configuration file automatically | |
50 | | -| planned | decide on which version update you want to be notified (major, minor, patch or other version regex) | |
51 | | -| planned | include alpha, beta, and release candidate versions and allow users to specify which version to track | |
52 | | -| planned | scheduling for periodic checks (daemon mode) | |
53 | | -| planned | custom Chat Cards for Sinks (if supported) | |
54 | | -| planned | alpha, beta, and release candidate versions | |
55 | | -| planned | give Veno a repo address where the config file is located. this allows veno to pull and update the config file. | |
56 | | -| planned | multiple config files for different teams (including repos with config files) | |
57 | | -| planned | script file template to run commands for veno which runs in a k8s pod | |
58 | | -| planned | Be able to split artifact and notifier definitions and merge them. So that different teams can maintain their own configs | |
59 | | -| planned | Make the version logic more robust (own crate; schema detection; schema logic, etc.) | |
60 | | -| planned | Option to also notify with the changelog or just the link to the changelog | |
| 43 | +| Status | Features | |
| 44 | +| ---------- | ------------------------------------------------------------------------------------------------------------------------- | |
| 45 | +| 🔜 Planned | make notifiers have references to artifacts so that only one message is being sent to the sink for multiple artifacts | |
| 46 | +| 🔜 Planned | yaml config support | |
| 47 | +| 🔜 Planned | toml config support | |
| 48 | +| 🔜 Planned | implement a config linter (check if notifiers, sources and references are valid) | |
| 49 | +| 🔜 Planned | Web endpoint to silence notifications for a specific artifact | |
| 50 | +| 🔜 Planned | update the current_version field in the configuration file automatically | |
| 51 | +| 🔜 Planned | decide on which version update you want to be notified (major, minor, patch or other version regex) | |
| 52 | +| 🔜 Planned | include alpha, beta, and release candidate versions and allow users to specify which version to track | |
| 53 | +| 🔜 Planned | scheduling for periodic checks (daemon mode) | |
| 54 | +| 🔜 Planned | custom Chat Cards for Sinks (if supported) | |
| 55 | +| 🔜 Planned | alpha, beta, and release candidate versions | |
| 56 | +| 🔜 Planned | give Veno a repo address where the config file is located. this allows veno to pull and update the config file. | |
| 57 | +| 🔜 Planned | multiple config files for different teams (including repos with config files) | |
| 58 | +| 🔜 Planned | script file template to run commands for veno which runs in a k8s pod | |
| 59 | +| 🔜 Planned | Be able to split artifact and notifier definitions and merge them. So that different teams can maintain their own configs | |
| 60 | +| 🔜 Planned | Make the version logic more robust (own crate; schema detection; schema logic, etc.) | |
| 61 | +| 🔜 Planned | Option to also notify with the changelog or just the link to the changelog | |
0 commit comments