Previously, I have handled renames of config modules in the Ubuntu packaging.
However, that means that really just throws that maintenance onto the packager. It'd be much nicer if cloud-init handled it somehow. The specific motivation for this is [1]. If the packaging doesn't change to address it, the new "package-update-upgrade-install" would be run again as it has never been run before.
The things I'd like to have:
* ability to specify that
* apt-update-upgrade was split into 2 pieces: apt-configure, package-update-upgrade-install
* foo changed in name to bar
* it looks like semaphores can contain '-' in them, based on their name in the config. Also, the config is inconsistent even in itself with respect to usage of '_' or '-'. I'd like to be consistent in the config (config/cloud.cfg) and enforce that 'set_hostname' is the same as 'set-hostname'.
--
[1] https://code.launchpad.net/~harlowja/cloud-init/pkg-up-install-goodies/+merge/130019
I talked with harlowja about this and we agreed that it makes sense to at least look at a 'cc_fixup' module that would run first, and it would go through and apply updates. psuedocode:
if module_
mark_
if module_
mark_ran("bar")
Where 'mark_ran' might even put the cloud-init version that applied the change.