Comment 1 for bug 1771433

FWIW that is because download/show/remove *must* be talking about the
remote backup, while "restore-backup" might be talking about a local one or
a remote one.
If we move to not storing backups on the controllers by default, then none
of download/remove/show become useful because there is nothing for them to
operate on.

On Wed, May 16, 2018 at 1:14 AM, Peter Matulis <email address hidden>
wrote:

> Public bug reported:
>
> The following backup commands do not require the use of the '--id='
> option when specifying a remotely-stored (on the controller) backup
> archive:
>
> download-backup
> remove-backup
> show-backup
>
> However, strangely, this command does:
>
> restore-backup
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
>
> ** Tags: backup-restore docteam
>
> ** Description changed:
>
> - The following backup commands do not require the use of the '--id=='
> + The following backup commands do not require the use of the '--id='
> option when specifying a remotely-stored (on the controller) backup
> archive:
>
> download-backup
> remove-backup
> show-backup
>
> However, strangely, this command does:
>
> restore-backup
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1771433
>
> Title:
> Backup commands are inconsistent when referring to remote backups
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1771433/+subscriptions
>