{"push_id":2635734976,"size":1,"distinct_size":1,"ref":"refs/heads/feature/sync-command","head":"71cc2ffdcb4cd9a0bb690c470f09c30b8b43148c","before":"c7745741406834f7dafac3b9da50f218366f055a","commits":[{"sha":"71cc2ffdcb4cd9a0bb690c470f09c30b8b43148c","author":{"name":"Michael Bridgen","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@weave.works"},"message":"Add `fluxctl sync` command\n\nThis adds the ability to manually trigger a sync (pull commits from\nthe git origin, and apply to cluster), and a command `fluxctl sync`\nwhich triggers a manual sync and reports its progress.\n\nSince a sync is potentially a long-running task, it's run using the\njob machinery: the command posts an `update.Spec`, which is submitted\nas a job and the ID returned. The command then proceeds more or less\nas it would for a release or policy change.\n\nBecause the different kinds of update require different handling, I've\nfactored the creation of jobs out into some combinators (or near\ncombinators):\n\n - run a job that needs a git clone\n - run a job that results in a commit, and report the result back to\n   the upstream server","distinct":true,"url":"https://api.github.com/repos/weaveworks/flux/commits/71cc2ffdcb4cd9a0bb690c470f09c30b8b43148c"}]}
{"actor":{"display_login":"squaremo"}}