should consume /etc/cloud.cfg.d files just like user-data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
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/
With this, there are some things I'm explicitly looking to support:
* DataSourceNone fully defined with 'runcmd' and the like inside of /etc/cloud/
So that you could easily boot an image with 'cloud-config-url' (which gets shoved into /etc/cloud/
as your sole source of metadata.
* putting '#!' or other content there.
* supporting the more intelligent merging routines (bug 1023179)
| $ cat 01-mystuff.cfg
| #cloud-
| - type: text/cloud-config
| content: |
| runcmd:
| - my-first-cmd
| $ cat 02-mystuff.cfg
| #cloud-
| - type: text/cloud-config
| merge-routine: append
| content: |
| runcmd:
| - my-second-cmd
Changed in cloud-init: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in cloud-init: | |
importance: | Medium → Wishlist |
Tracked in Github Issues as https:/ /github. com/canonical/ cloud-init/ issues/ 2324