I have one more related request that I didn't think of when I originally wrote this report. I'd like to be able to detect that an installed system _will_ write to the new path in /run if nothing is there right now, so that I can detect when I can wait for that file and when I must fall back to my previous hacks. Maybe a test for a file, or a way to run --version against something? dpkg-query seems a bit too Debian/Ubuntu -specific to me. Is running "cloud-init --version" acceptable to use with a no API breakage guarantee?
Alternatively any other way to fix my hack so detection works for both cloud-init with this new feature and on old releases using older cloud-init using the same script in both cases would be fine.
That looks good - thanks!
I have one more related request that I didn't think of when I originally wrote this report. I'd like to be able to detect that an installed system _will_ write to the new path in /run if nothing is there right now, so that I can detect when I can wait for that file and when I must fall back to my previous hacks. Maybe a test for a file, or a way to run --version against something? dpkg-query seems a bit too Debian/Ubuntu -specific to me. Is running "cloud-init --version" acceptable to use with a no API breakage guarantee?
Alternatively any other way to fix my hack so detection works for both cloud-init with this new feature and on old releases using older cloud-init using the same script in both cases would be fine.
Right now my hack looks like this: http:// bazaar. launchpad. net/~uvtool- dev/uvtool/ trunk/view/ head:/remote- wait.sh
No rush as I won't try and make Vivid for this since the current hack works OK. I can fix this next cycle though.