Can we get ~ expansion for --env-file in op run?

semanticart
semanticart
Community Member
in CLI

I'd prefer to be able to use op run --env-file="~/envs/example.env" to op run --env-file="/Users/me/envs/example.env" but right now I get

[ERROR] 2023/12/07 11:43:47 open ~/envs/example.env: no such file or directory

I know I can use $HOME but tilde expansion feels pretty natural for a CLI tool.

Thanks!

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: current OSX
Browser: Not Provided

This discussion has been closed.