| 2018-05-16 12:15:50 |
Peter Matulis |
description |
The backup files that get downloaded to the local client by means of the `create-backup` command should, by default, reflect the name of the corresponding controller. Otherwise, backups made on multi-controller setups become indistinguishable. Below, there are two backups for an 'lxd' controller and one for the 'aws' controller:
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:20 juju-backup-20180515-191942.tar.gz
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:40 juju-backup-20180515-193724.tar.gz
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:58 juju-backup-20180515-195557.tar.gz
The user should not have to rely on the `--filename` option to overcome this confusion. I would expect to see, by default:
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:20 juju-backup-aws-20180515-191942.tar.gz
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:40 juju-backup-lxd-20180515-193724.tar.gz
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:58 juju-backup-lxd-20180515-195557.tar.gz |
The backup files that get downloaded to the local client by means of the `create-backup` command should, by default, reflect the name of the corresponding controller. Otherwise, backups made on multi-controller setups become indistinguishable. Below, there are two backups for a controller named 'lxd' and one for a controller named 'aws':
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:20 juju-backup-20180515-191942.tar.gz
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:40 juju-backup-20180515-193724.tar.gz
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:58 juju-backup-20180515-195557.tar.gz
The user should not have to rely on the `--filename` option to overcome this confusion. I would expect to see, by default:
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:20 juju-backup-aws-20180515-191942.tar.gz
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:40 juju-backup-lxd-20180515-193724.tar.gz
-rw-rw-r-- 1 ubuntu ubuntu 56M May 15 19:58 juju-backup-lxd-20180515-195557.tar.gz |
|
