Comment 6 for bug 1883122

Aha, OK, one part I missed: we have a specific use case which wants these distinct "disabled" states to be machine readable. From my perspective, the current output doesn't meet that requirement for a couple of reasons: (a) for me, the detail text is intended for human consumption (consider how you would have to parse that reason out: `disable_reason = detail.split("disabled by")[1]`) but, probably more importantly, (b) this still requires consumers to enumerate the ways in which cloud-init can be permanently disabled, which will fall down if we add a new method by which cloud-init can be disabled.