Comment 4 for bug 1883122

There's also `cloud-init status --long` which should have reported to folks the reason for disabling such as 'Cloud-init disabled by /etc/cloud/cloud-init.disabled'

I think there is also a bug here in that behavior because currently on a disabled container which has already run cloud-init once, we report both the detected datasource details and the disabled state.

$ cloud-init status --long
status: disabled
time: Fri, 12 Jun 2020 20:00:51 +0000
detail:
DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]

I think we can definitely provide a better assessment of the machine state and separation of current_status versus next_boot status, or is_enabled as James mentioned.