More explicit reporting of the status of encrypted files

[TheLocehiliosan]

This feature request has been pulled out of Issue #69.

More explicit reporting of the status of encrypted files

I think it'd help to have either a separate command (yadm status-encrypted) or overlay a flag on yadm status (yadm status --encrypted) that collects a modular set of smaller reports that convey as much as possible about the exact status of every file that is in the current blob or matches encrypt. This can require the decryption password; but if decryption time is too tedious for some uses, a separate encrypted file could just store metadata about the paths in the blob. (While thinking about how to generate this, I wondered if the encrypted blob could be/hold its own .git repo, though that might make older copies of sensitive information too durable.)

This information would be most useful appended/inlined for relevant git commands:

• append a small report on encrypt paths that are either out of sync with or will be updated by the current encrypted blob toyadm status, and one on paths that are safely up-to-date in the committed encryption blob and paths that still need action to yadm status -u.
• filter output from some git commands (particularly yadm status -u) to wrap encrypt paths with new colors or typographic indications of their status.

[github-actions]

This issue has been labeled as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.