non-interactive add-cloud discards existing description

[Aaron Bentley]

non-interactive add-cloud drops the existing description field.
(This is different from bug #1645783, where *interactive* add-cloud doesn't *prompt* for a description field.)

This is similar to a known bug that update-clouds discards this description field, and probably has the same root cause.

Since add-cloud is used with private clouds, for which a generic built-in description is typically unsuitable (and vsphere and manual don't even have generic built-in descriptions), discarding this field is much worse than the update-clouds case.

Tested with revision-build 4160/7b7d4a4
$ `jver 2.1-4610` add-cloud vsphere ~/canonical/cloud-city/example-clouds.yaml
$ cat $JUJU_DATA/clouds.yaml
clouds:
  vsphere:
    type: vsphere
    auth-types: [userpass]
    endpoint: 10.245.0.131
    regions:
      dc0:
        endpoint: 10.245.0.131
$ cat ~/canonical/cloud-city/example-clouds.yaml
clouds:
  vsphere:
    type: vsphere
    auth-types: [userpass]
    endpoint: 10.245.0.131
    regions:
      dc0:
        endpoint: 10.245.0.131
    description: 'foo'
$ `jver 2.1-4610` --version
2.1-beta2-xenial-amd64

[Anastasia (anastasia-macmood)]

Marked as Won't Fix for 2.0.x as no further 2.0.x releases are planned.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.