Add the ability to restart a run or some of its tasks updating the task variable data. This could be useful if some variables have changed (like auths) so we want to update them and then restart the failed tasks.
Run restart logic is done inside the runservice and the runservice is made to don't know anything of the upper layers (webhook, git, configstore data) and for this reason it receives the tasks envs and docker auths already populated by the upper layer (currently the gateway).
So we should:
Save the original config somewhere (directly inside the runconfig as an annotation but this could increase a lot its size at every load or perhaps in a dedicated entry that could be loaded only when needed)
Recreate the runconfig tasks that we want to restart and send them to the runservice when calling the recreaterun api
The runservice on a recreaterun request could verify and update the task Environment and DockerRegistryAuth task entries)
huapox
commented
4 years ago
Add the ability to restart a run or some of its tasks updating the task variable data. This could be useful if some variables have changed (like auths) so we want to update them and then restart the failed tasks.
Run restart logic is done inside the runservice and the runservice is made to don't know anything of the upper layers (webhook, git, configstore data) and for this reason it receives the tasks envs and docker auths already populated by the upper layer (currently the gateway).
So we should:
EnvironmentandDockerRegistryAuthtask entries)