Comment 1 for bug 1930184

We'll need to figure out the best approach here since there's a compatibility issue changing field names. At first glance, Juju seems at "fault" here as it takes the raw feed from the API and renames the fields. At least that's the case for the one I looked at "instance-status" becomes "machine-status". Juju would have renamed the output to conform with modelling decisions and it did so on the client side to preserve api compatibility. I think my preference would be to change libjuju to match juju. libjuju could get the renamed fields added as new fields and then remove the old ones in juju 3.0. On that basis this but would be a "Won't Fix" for juju but will leave open till we agree on the approach.