Runner updates, runner side: flow runner update --from FILE issue #85 closed: completed andymccall opened this · 0 comments
andymccall set labels feature ·
closed by change 85275e1ef3b7 ·
andymccall set labels feature ·
closed by change 85275e1ef3b7 ·
First step of the self-updating runners design (docs/jetstream.md §8.2, issue #84): with a local build, check it (this machine's target, it runs, --version and tiers), stage it as flow.new, swap it in keeping flow.prev, and have the running runner leave with notice (finish what fits, hand back the rest with checkpoints) so its unit starts the new build. The new build proves itself by reaching the hub; three failed starts or ten minutes without the hub restore flow.prev. A runner's flow.toml can refuse updates ([runner.update] allow = false). --dry-run checks and says what would happen.