Some questions regarding 1Password CLI and winget
I've been using 1Password CLI since it's initial release and just now I figured I would check if there's some smoother way of managing updates of the application.
As of now, the steps for updating are 1) running op update 2) downloading the new update 3) unzipping the file 4) moving op.exe to C:\Program Files\1Password CLI 5) deleting the downloaded files and 6) running op update to verify the update. I want to cut that down to just run winget upgrade "1Password CLI".
In the https://developer.1password.com/docs/cli/get-started#step-1-install-1password-cli I see that it's available as a package through winget. I searched the forum and found some threads with feature requests for making the application available on winget, but the threads I looked at mentioned that it was on the roadmap and that packages that already were available on winget were community maintained. Is that still the case or is the package managed by 1Password now since that installation method is listed in the docs?
So far I've used the manual installation method for installing and updating the application. Can I "switch" to the winget package easily and will it just take over from my manual install, or are there any caveats to consider? For example, I have my own account and a service account configured to use the current 1Password CLI installation. The service account is used in conjunction with some scripts that run on a schedule. Will the accounts and scripts continue to work or will I have to configure everything from scratch again?
I could just try and see what happens, but as I thought it was somewhat of a hassle to get everything configured, I'd rather post a question here first.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided