Open
Description
Description
When a Chocolatey license is due to expire, Chocolatey Central Management users who log in will be notified of the expiration. The period when those notifications are sent is fixed.
The period when license expiration notifications start to appear should be configurable. However, to ensure that the license does not expire without the user being aware, so the notification period should have a minimum value of 14 days and a realistic maximum value of 365 days.
Why Is It Needed
The notification could end up just being unnecessary "noise" for the administrators that log in.
Related Issues and Tickets
N/A
Acceptance Tests
- Set the license expiration notification to 366 days and see that CCM rejects the value and sets it to 365 and warns the user that the notification period is a maximum of 365 days.
- Set the license expiration notification to 13 days and see that CCM rejects the value and sets it to 14 and warns the user that the notification period is a minimum of 14 days.
- Set the license expiration notification to 0 days and see that CCM rejects the value and sets it to 14 and warns the user that the notification period is a minimum of 14 days.
- Set the license expiration notification to 300 days and see that CCM accepts the value.
a. License Chocolatey Central Management with a license that is due to expire in less than 300 days and ensure notifications of the expiration are sent.
b. License Chocolatey Central Management with a license that is due to expire in more than 300 days and ensure notifications of the expiration are not sent.
Done Checklist
- Documentation has been updated?
- Automated tests have been added to cover this?
- Manual tests have been added to cover this?
- ADR created to document the design / decision?
- Title is suitable for using in Release Notes?
┆Issue is synchronized with this Gitlab issue by Unito