{"push_id":2313558484,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"2e886c9efdc76dba02ce805b61e0663c1bd4728d","before":"37dfbe3a23299c62edb8f2a8c159cac1b2ad795a","commits":[{"sha":"ea5abd71f6bdf3ffd8fa8122e049b90091e0e90a","author":{"name":"Michael Bridgen","email":"844aface8de49b32585c3c744b570659f1739c56@weave.works"},"message":"Symlink regenerated secret key to expected path\n\nWe now include an ssh_config file in the image, to avoid having to\nsupply the identity file path on the command line each time.\n\nThe way keys are generated means that it's possible the key won't\nalways be at the path that's in that config\n`/etc/fluxd/ssh/identity`. If there's no key when the daemon starts\nup, or you regenerate it, the daemon will create one in a\ntmpfile. Eventually, at least on the next reboot, it will be mounted\nat the expected path; but in the meantime, the ssh_config will be\nlooking at the old key.\n\nTo fix this, maintain the symlink at the expected path so that the\nexpected path is _always_ the latest key. Since we cannot update the\nk8s secret and move the link atomically, this means regenerating the\nkey can fail partially, updating the secret but leaving the symlink\nwhere it is. The trade-off is that the key is at a stable position.","distinct":false,"url":"https://api.github.com/repos/weaveworks/flux/commits/ea5abd71f6bdf3ffd8fa8122e049b90091e0e90a"},{"sha":"2e886c9efdc76dba02ce805b61e0663c1bd4728d","author":{"name":"Michael Bridgen","email":"51def41f3b867ba43c7f77708ded5b71ff83e30b@squaremobius.net"},"message":"Merge pull request #903 from weaveworks/link-secret-key\n\nSymlink regenerated secret key to expected path","distinct":true,"url":"https://api.github.com/repos/weaveworks/flux/commits/2e886c9efdc76dba02ce805b61e0663c1bd4728d"}]}
{"actor":{"display_login":"squaremo"}}