yahoo-eng-team team mailing list archive

[James Falcon <1078770@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2324

** Bug watch added: github.com/canonical/cloud-init/issues #2324
   https://github.com/canonical/cloud-init/issues/2324

** Changed in: cloud-init
       Status: Triaged => Expired

-- 
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/1078770

Title:
  should consume /etc/cloud.cfg.d files just like user-data

Status in cloud-init:
  Expired

Bug description:
  It seems like it makes sense to extend the files in /etc/cloud.cfg.d to be able to contain the same data that user-data can have.
  There would be some exceptions (not allowing remote '#include' or '#include-once').

  That would allow you to just put stuff in that directory rather than
  /var/lib/cloud/data/seed and the like.

  With this, there are some things I'm explicitly looking to support:
   * DataSourceNone fully defined with 'runcmd' and the like inside of /etc/cloud/cloud.cfg.d
     So that you could easily boot an image with 'cloud-config-url' (which gets shoved into /etc/cloud/cloud.cfg.d)
     as your sole source of metadata.
   * putting '#!' or other content there.
   * supporting the more intelligent merging routines (bug 1023179)
     | $ cat 01-mystuff.cfg
     |   #cloud-config-archive
     |   - type: text/cloud-config
     |     content: |
     |       runcmd:
     |         - my-first-cmd
     | $ cat 02-mystuff.cfg
     |   #cloud-config-archive
     |   - type: text/cloud-config
     |     merge-routine: append
     |     content: |
     |       runcmd:
     |         - my-second-cmd

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