Pipeline retention periods cannot be configured for longer than 1 year
The Problem
Some customers may want to configure retention periods longer than 1 year. We currently enforce a retention window between 1 year and 1 day. As a space management feature, telling customers that they can only have retention periods less than 1 year, or else they can't use the feature, may not be a great experience.
(A) Proposal(s)
- Extend the top end of the setting boundary to a greater number of years.
Considerations
We have not yet implemented Allow instance administrators to configure CI d... (#519688). If we're going to extend this window on gitlab.com for our SaaS customers, it would be a better experience for us set our PlanLimits first. If we allow people to configure a long retention window now, implementing the PlanLimit later will be taking away something that they've already configured.
We should decide how much retention to allow per plan level for our own customers and then allow the generic setting to be extended, e.g. to 10 years, which we might not want to allow for everyone.