← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1075980] Re: upstream should handle cc_ renames

 

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1075980

Title:
  upstream should handle cc_ renames

Status in Init scripts for use on cloud images:
  Fix Released

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1075980/+subscriptions