Comment 5 for bug 1883122

As Chad mentions, status --long shows this state:

% touch /etc/cloud/cloud-init.disabled
% reboot
% cloud-init status --long
status: disabled
detail:
Cloud-init disabled by /etc/cloud/cloud-init.disabled

root@g1:~# rm -rf /etc/cloud/cloud-init.disabled
root@g1:~# mv /var/lib/cloud/seed/nocloud-net /root/
root@g1:~# reboot
root@g1:~# ..:(╯°□°)╯彡┻━━┻
(crispyboi) ~ % lxc exec g1 bash
root@g1:~# cloud-init status --long
status: disabled
detail:
Cloud-init disabled by cloud-init-generator

So, this feels like enough to me... But maybe we should incorporate some additional message to convey that the former test (cloud-init.disabled) means future boots will not run cloud-init at all and the latter means cloud-init will run detection code.