Draft: Store the most recent deployment job's auto_stop_in on the environment
What does this MR do and why?
Store the most recent deployment job's auto_stop_in on the environment
When an environment is configured with an auto stop time, CI jobs for
the environment that use the prepare or access action will cause
the stop time to be recalculated using the value that was originally
used to set it. This value is stored as metadata (Ci::BuildMetadata)
associated with the most recent deployment job.
With this change the value is now stored on the environment record itself. This means the auto stop time can be recalculated without having to fetch metadata from an old job, which in turn allows the metadata to be removed without losing the ability to recalculate the timer.
Changelog: other
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #545659 (closed)