CLI Installation via Homebrew Cask Requires Sudo and so Can't be Unattended
To install the 1Password CLI the best instructions are to use brew install --cask 1password-cli. But as a cask what this does is download and run a macOS installer package. This in turn requires sudo to install op into /usr/local/bin. But this install (and thus update) process cannot be done with, say, running the standard Homebrew update and upgrade commands in a lanuchd job once weekly, since while everything else gets updated, the process gets stuck when needing sudo for the cask.
Is there a specific reason the op command is a cask and not a normal formula that would update just fine unattended and live within the Homebrew prefix (/opt/homebrew on Apple Silicon)? This would both allow us to run updates to all Homebrew-installed tools unattended, but frankly also just makes more sense in terms of where it gets installed seeing that op is just a single command line tool.
1Password Version: CLI 2.14.0
Extension Version: Not Provided
OS Version: macOS 13.2.1
Browser:_ Not Provided