Allow collation/partitioning of notifications based on expiry and path

[dennisjbell]

It would be really great if notifications could be sent different shout targets based on the path of the expired certs. This is mainly because groups of certs are handled by different teams in an organization. Furthermore, (and I confess to no knowing if this is already the case or not) it'd be best if the notification was grouped for all expired (or expiring) certs under that path and expiry timeframe, similar to the current dashboard's expired, in 2 week, in 4 weeks.

[thomasmitchell]

I would imagine this would require path specification by a list of path( regex)?s to include and exclude, such that you could say "these branches notify here, but this branch inside that branch doesn't, and instead goes over THERE".

As for the notification, right now, the notification system checks on a specified schedule to see if anything is worth warning about, and if so it gives a message that things are either "expiring soon" or "expired". The notification also contains a link to the doomsday itself, and basically tells you to go check it out. It doesn't list the offenders in the notification at this time. That's something I'm not really sure what the right way to handle is - I don't want to blast a giant TL;DR notification, but I also don't want people to start ignoring the alerts because they just say "expiring soon" for like... 4 weeks straight, when "expiring in 4 weeks" is actually very different than "expiring in a couple hours"

[7hunderbird]

Similarly, could it be possible to group certs by path in the UI? So I can click on secret/c/ops/vault for Vault or secret/c/ops/bosh for BOSH.

[thomasmitchell]

@7hunderbird This is a thing I've wanted for awhile - basically the ability to specify a regex to match paths to group on that can be used for collation. Right now, I'm in the middle of the slow process of converting the Web UI to Vue so that I can iterate on features like that a bit faster. I'd appreciate it if you could open up that feature request as a separate issue.

[7hunderbird]

Created #39.