bad initialization for importers

[brmzkw]

In backup.go, we attempt to initialize the importer. In case of failure, we fallback to the fs importer.

If the importer fails because the path given is invalid, we should instead display the error to the user.

[poolpOrg]

Can you show me how to reproduce, I'm unsure I understand the issue

[brmzkw]

Let's say the s3 importe fails during initialization. The error is bubbled up, but then, we fallback to the fs importer in backup.go.

As a result, creating a snapshot of an invalid s3 location successfully creates a backup:

./plakar backup s3://sadfoinansdiofnoais
Duration: 0s
Directories: ✓ 1
      Files: ✓ 0
Done!
info: created unsigned snapshot b22ec89f with root pQBOyJRN59VQ5levAhIACig/hs3S3dOMYt5ZIeW/MYc of size 0 B in 1.240125ms

[ptr-math]

Yeah it's a known shortcoming of our current (best) heuristic to process both absolute and relative paths for the fs. Not something we can easily fix without doing a full re-make of how we handle backend detection (same goes for repo/exporter).

The remake is in a todo list somewhere, but it's def. a post V1 thing.