Drop legacy finished at in Deployment
What does this MR do and why?
Realized this behavior while evaluating !71767 (merged) as a solution for #29884 (closed).
We introduced the legacy_finished_at
for the transition period (From stateless to stateful), however, since finished_at
backfill has already been completed, we no longer need this fall-back code. Rather, it's causing a bug that displaying a wrong finished_at
for existing deployments. Therefore, we should drop the legacy code.
Related #350618 (closed)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Shinya Maeda