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

Bug #1078770 reported by Scott Moser on 2012-11-14
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cloud-init
Wishlist
Unassigned

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

Scott Moser (smoser) on 2012-11-14
Changed in cloud-init:
status: New → Triaged
importance: Undecided → Medium
Dan Watkins (oddbloke) on 2019-03-06
Changed in cloud-init:
importance: Medium → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers