Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Release 3.1.0 #175
referenced this pull request
Mar 13, 2019
My ideal case, which may be mis-informed, is that once this update goes in, provided azure is identified as the oem id on the kernel command line, all the needfuls will happen on a *COS system to keep in online in Azure. Likewise for packet.
If that means including the unit file, then I think my answer is yes.
Yeah, definitely no doubt we need a systemd unit somewhere. My question was more about where. :) It'd be nice to keep it here, but I'd like to confirm the interactions with CL since we probably don't want to change how check-in works there at this point. (Or do we?)
@jlebon I think that the service file could live here (next to the existing one). However I think that right now it is quicker to tag this, add the unit via RPM packaging, test everything and then move the unit to here once everything is confirmed ok. If no objections, I'll proceed with the release.