Persistent op run Rather Than Manually Calling it
This is kind of a far out there suggestion, and so I know unlikely, but one challenge with op run
when protecting secrets with it is remembering to use it. For example, I am protecting my Linode API token in 1Password and referencing it in an environment variable, but many times forget to preface linode-cli ...
with the requisite op run
command the first time I try something in a given session. What if there could be some form of integration into shells that would always check for the secrets reference syntax and replace those with data from 1Password items? By its nature of needing shell config modifications this'd be opt-in, but may be worth considering. I do like that I can use 1Password to protect secrets needed on the command line, but I just find myself forgetting that I've done this, especially if I'm pasting in a command from documentation or other sources. I don't see any hint of this in the CLI 2 docs, so wanted to at least make the feature suggestion.
1Password Version: 8.6.0-43.BETA
Extension Version: 2.2.3
OS Version: macOS 12.2.1