Enforce a time gap between turning ON a Feature Flag 100% on staging and then on production
With #113, we will ensure that a FF is ON 100% on staging before we can turn it on in production. But we also want to avoid turning ON a FF on staging and then on production right away. There should be a time gap between the two events.
At the least, the gap should allow enough time for one full end-to-end test suite run and its results evaluated by the Quality pipeline triage DRI. To be on the safe side, I think 24 hours should be fine.
This restriction should be overridable.
Edited by Sanad Liaquat