Optional Age Folder Location #72
Description
For context, my current pvetui configuration is storing the config YAML file along with cache_dir within a separate internal SMB share -- this allows me to share pvetui functionality between multiple internal hosts without duplicating API token configurations or storing duplicate configurations on hosts.
With that said, upon setting up a new personal workstation I was confused when trying to use pvetui with the configuration file stored on my SMB share resulted in an "authentication failed: invalid credentials" error message. After checking multiple times between my hosts, literal same verbatim syntax but getting a different result, I realized that the working workstation had .age-identity and .age-recipient files within $env:APPDATA despite my pve_cache being stored elsewhere.
To be fair, I am unfamiliar with age encryption, but after looking through the codebase (specifically encryption.go) and skimming through the age Github project -- I learned my invalid credentials message had to do with my new workstation not having the proper .age-identity and .age-recipient files stored within %appdata%.
With all that said, would an optional age file location location within the config file be feasible? I recognize it may not be the most secure approach in the world, but a verbose override would be greatly appreciated. On one hand, it could be stored in the cache_dir by default (though I'd wager the --no-cache parameter would result in some issues), but also adding an optional age_folder within the config file could also prevent this.
pvetui versions tested are versions 1.0.12 - 1.0.15, all built from source via go install on both Windows 24H2 and 22H2. Happy to include more information if needed, as well as admit this is a very niche case and implementation may be low priority.