{"push_id":2636833948,"size":1,"distinct_size":1,"ref":"refs/heads/after-cloud-init","head":"17e1809494facc0904c390949dd1f2a36437540d","before":"8a05fab1b341c5ddbeee00093440dc6edd28d9f7","commits":[{"sha":"17e1809494facc0904c390949dd1f2a36437540d","author":{"name":"Jacob Vallejo","email":"c9c13a35dd80a3610ba6d11c0fca731e4d5563ab@amazon.com"},"message":"Start ecs.service after user data evaluation\n\nThis change ensures `ecs.service` start after `cloud-final.service`,\nthe last cloud-init stage (see below docs link [0]), for user data\nconfiguration of ecs-init. There are transitive `Require`s and `Wants`\nfrom other dependent units (ie: though `docker.service`) that achieve\na desired ordering however including `After=cloud-final.service`\nensures dependent units' ordering do not change `ecs.service`'s order\nrequirement.\n\n[0]: https://cloudinit.readthedocs.io/en/0.7.9/topics/boot.html","distinct":true,"url":"https://api.github.com/repos/jahkeup/amazon-ecs-init/commits/17e1809494facc0904c390949dd1f2a36437540d"}]}
{"actor":{"display_login":"jahkeup"}}