[EPIC] Compliance Monitor: improve architecture and quality of life, add features #633
Open
3 of 5 tasks
Labels
Milestone
The following sections are to keep notes about ideas for future developments; they will each be turned into issues before work starts.
Improve architecture
Quoting @martinmo:
Of course, I totally agree -- now that we have a running deployment (which goes a long way to show that the approach is viable), some real structure is in order!
Quality of life improvements
zuul-cli
, change multiple config files, restart the service etc.Tasks:
Introduce badges
The table currently lists all versions of the scope that the subject complies with, instead of showing a badge; we should convert this list into a badge as follows:
Maybe the list is not sufficient to compute the badge, because it doesn't tell us anything about versions that could have been complied with, but for some reason, some test results are missing. Then the question is: why are they missing? If the test couldn't complete due to unreliable infrastructure, then it's a bug on the end of the test subject, and the badge can as well be red. If, however, the test couldn't complete due to a programming error on our end, then we better use the grace period of 7 days to fix it, and then a grey badge would also be wrong. So, I think we can actually proceed with the list-to-badge-conversion as outlined above.
Add Prometheus exporter
(if there is demand?)
The text was updated successfully, but these errors were encountered: