-
Notifications
You must be signed in to change notification settings - Fork 852
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upstream should handle cc_ renames #2315
Comments
Launchpad user Scott Moser(smoser) wrote on 2012-11-07T18:53:29.728707+00:00 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: Where 'mark_ran' might even put the cloud-init version that applied the change. |
Launchpad user Scott Moser(smoser) wrote on 2012-11-07T18:53:54.895911+00:00 it could also go through any semaphores with '-' in their name and canonicalize them. |
Launchpad user Joshua Harlow(harlowja) wrote on 2012-11-08T07:22:28.100017+00:00 https://code.launchpad.net/~harlowja/cloud-init/migrator-module/+merge/133409 should be doing this now also. |
Launchpad user Scott Moser(smoser) wrote on 2012-11-12T18:07:45.017429+00:00 this was fix-committed in revno 710. |
This bug was originally filed in Launchpad as LP: #1075980
Launchpad details
Launchpad user Scott Moser(smoser) wrote on 2012-11-07T14:54:16.438947+00:00
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
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
The text was updated successfully, but these errors were encountered: