backup -- ls: shows too many paths? #37

New Issue

decentral1se · 2023-10-12T13:41:46Z

decentral1se commented

2023-10-12 13:41:46 +00:00

I think I would not expect the timestamps?

And further, the lines with /var, /var/lib etc.

🌻 ./abra app backup ls abra-test-recipe.foo.com
2023-10-12T13:33:57.595887937Z /secrets
2023-10-12T13:33:57.595887937Z /secrets/abra-test-recipe_foo_com_pass_one_v1
2023-10-12T13:33:57.595887937Z /secrets/abra-test-recipe_foo_com_test_pass_two_v1
2023-10-12T13:33:03.084078341Z /var
2023-10-12T13:33:03.084078341Z /var/lib
2023-10-12T13:33:03.088078326Z /var/lib/docker
2023-10-12T13:33:02.108081747Z /var/lib/docker/volumes
2023-10-12T13:24:40.985842291Z /var/lib/docker/volumes/abra-test-recipe_foo_com_test-volume
2023-10-12T13:24:40.985842291Z /var/lib/docker/volumes/abra-test-recipe_foo_com_test-volume/_data

Maybe something like?

🌻 ./abra app backup ls abra-test-recipe.foo.com
/secrets/abra-test-recipe_foo_com_pass_one_v1
/secrets/abra-test-recipe_foo_com_test_pass_two_v1
var/lib/docker/volumes/abra-test-recipe_foo_com_test-volume/_data

Also, it would be good to include the time/date of this backup? Is there also an accompanying snapshot ID or additonal metadata you think would be useful to have on the receiving end of this?

I think I would not expect the timestamps? And further, the lines with `/var`, `/var/lib` etc. > 🌻 ./abra app backup ls abra-test-recipe.foo.com > 2023-10-12T13:33:57.595887937Z /secrets > 2023-10-12T13:33:57.595887937Z /secrets/abra-test-recipe_foo_com_pass_one_v1 > 2023-10-12T13:33:57.595887937Z /secrets/abra-test-recipe_foo_com_test_pass_two_v1 > 2023-10-12T13:33:03.084078341Z /var > 2023-10-12T13:33:03.084078341Z /var/lib > 2023-10-12T13:33:03.088078326Z /var/lib/docker > 2023-10-12T13:33:02.108081747Z /var/lib/docker/volumes > 2023-10-12T13:24:40.985842291Z /var/lib/docker/volumes/abra-test-recipe_foo_com_test-volume > 2023-10-12T13:24:40.985842291Z /var/lib/docker/volumes/abra-test-recipe_foo_com_test-volume/_data Maybe something like? > 🌻 ./abra app backup ls abra-test-recipe.foo.com > /secrets/abra-test-recipe_foo_com_pass_one_v1 > /secrets/abra-test-recipe_foo_com_test_pass_two_v1 > var/lib/docker/volumes/abra-test-recipe_foo_com_test-volume/_data Also, it would be good to include the time/date of this backup? Is there also an accompanying snapshot ID or additonal metadata you think would be useful to have on the receiving end of this?

decentral1se commented

2023-10-12 13:45:39 +00:00

Related #27

Related https://git.coopcloud.tech/coop-cloud/backup-bot-two/issues/27

decentral1se commented

2023-10-12 13:46:01 +00:00

@3wordchant any thoughts on output for this which would be useful?

moritz commented

2023-10-18 13:32:08 +00:00

I think for finding files with grep it would be nice to list all files recursively. But instead of being the default behavior, it could be activated with a flag like --all / -a . And the default behavior could be to provide a path, like unix ls works. And maybe activating timestamps with a -t flag?

I think for finding files with `grep` it would be nice to list all files recursively. But instead of being the default behavior, it could be activated with a flag like `--all / -a `. And the default behavior could be to provide a path, like unix `ls` works. And maybe activating timestamps with a `-t` flag?

👍 1 🎉 1

decentral1se commented

2023-10-18 14:53:20 +00:00

That sounds Very Cool @moritz 👍

Sign in to join this conversation.