backup commands misleading help

[Anastasia]

All backup related commands seem to extend ModelCommand and act as if they can be run against any model. However, in reality, they can only be run against one model - "controller".

This needs to be cleaned as part of the new "backup and restore" iteration since it is misleading and not user friendly.

For example, 'juju help create-backup' describes specifying a model - https://pastebin.ubuntu.com/p/nrgGw3xvD7/ - but actually specifying a non-controller model errs out with "ERROR backups are only supported from the controller model".

The same applies to:
* 'juju backups' which errs out with the same error as 'juju create-backup';
* 'juju show-backup' which errs out with the same error as 'juju create-backup';
* 'juju download-backup' and 'juju upload-backup' with "requested model is not the controller model";
* 'juju remove-backup' seems to connect to specified, non-controller model but, of course, there is no backup stored against this model (since we cannot create them), so it errs out at the end with an obscure "ERROR expected 1 result(s), got 0".

[Anastasia (anastasia-macmood)]

In fact, all this command need to be controller specific (i.e. provide --controller option) since a controller name can be provided at command line when non-current controller is desired.

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

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