How to debug glob inclusion/exclusions? Way to list files/dirs under consideration due to globs?

[vram0gh2]

Of course, let me start by thanking @aawsome and those who have contributed to this software. Thank you for your generosity!

What is the best way to understand what rustic is doing as it applies include/exclude globs to decide if files or directories are being considered for further processing (such as change detection)?

I'm looking for some sort of dry-run debugging type option that shows whether a file was or was not under consideration, and which globs were applied to reach that conclusion. Of course, such a listing would skip descending into directories that it had already marked for exclusion.

--log-level debug --dry-run seems to give a lot more information beyond this but does a lot more as well, including connecting to the remote repo. What I'm looking for would just need to do a local scan.

Is there such a way to get this? Unfortunately, the docs are a little barren and perhaps work better for those for whom rustic is already doing what they hope.

[aawsome]

Hi @vram0gh2!

Current nightly builds should have a much nicer default output when using --dry-run --log-level debug, see #1643.

Also, you can soon use rustic ls /local/dir (+ exclude options) to see how the excludes options will apply, see #1645.

[aawsome]

Listing files/dirs with glob and other excludes is now possible with the ls command (#1645).
This should be included in the next nightly build and in the upcoming 0.11.0 version.

[fvsch]

@aawsome That sounds great! Do you know if this would be usable with snapshot names? As in, rustic ls --name Documents.

I have configured snapshots with their own excludes (using globs) in addition to global exclude patterns (using backup.glob-files), so it can be useful to check how those combine on a per-snapshot basis.