For long-running deployments (such as with customers who hold deployments alive for years), it is possible that the deployment accumulates a large number of day-2 executions, making the executions list too long to make sense of.
Customer (c821) is asking for the possibility to delete past executions.
it’s possible, maybe it will be nicer to add some “save x last executions“ or “save only the last month’s executions“ logic
Do we rely, in any part of the codebase, on looking up past executions?
We will need to clean up connected data, like events, logs, dep update history, when we delete some execution. After that I think it will be ok, no?
Merged in master. Leaving open for now, for changes pending the removal of create_deployment_environment workflow