change the default to the nocloud data source
Bug #1546230 reported by
Sergio Schvezov
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Today, having cloud-init instead defaults to a data source that might not be the correct one, ideally cloud-init should have a sane default of the common denominator which would be a nocloud data source.
Revision history for this message
| Ben Howard (darkmuggle-deactivatedaccount) wrote | #1 |
| Changed in cloud-init: | |
| status: | New → Invalid |
| assignee: | nobody → Ben Howard (utlemming) |
Revision history for this message
| James Falcon (falcojr) wrote | #2 |
To post a comment you must log in.
Nack'ing this request. After discussing this idea with the server team offline, this is not desirable. For Snappy and images, livecd-rootfs and/or the image build process should drive the image specific cloud-init configuation.