Users should be able to set notification interval expiration about lemur

[andrewachen]

Context -- we renew at 14 days and alert at 10.

[kevgliss]

@andrewachen what granularity were you thinking? Is specifying an arbitrary number of days before notification enough? Would a numeric and a unit useful? (1d, 1w, 1m, 1yr)

[andrewachen]

Yes, numeric and a unit would be useful. For my use case, I'd be interested in alerting at 7d and 3d.

We also need the ability to acknowledge/mute an alert. For example, when we retire a site, I want to be able to manually squelch notifications for its certs.

[kevgliss]

Okay, this will most likely change the /certificate api adding a new optional value of 'notifications'. This would be a list of notifications that are associated with the newly created certificate. These notifications would be defined before hand and could be general or team specific. Think - my_team_notification_14_days, with a few recipients of the notification.

Certificates already have an 'active' flag, when marked as 'inactive' this will mute all associated notifications for that particular certificate.

Would this API addition warrant an API increment? Since it's optional I would think that this could be added without breaking any existing code.

I am hoping to have something for this this week.

[andrewachen]

I say it's not necessary to increment the version if it's a new optional field (as opposed to changing an existing field or making it required). My general rule of thumb is if existing code in the wild will continue to work after my API change, then no need to rev the api.