Not overwriting existing environment variables

Hello @REBELinBLUE,

Thank you for reaching out to us. I can reproduce the issue on my end, and 1Password does use the variable in shell instead of .env file. I will report it to my team for further investigation. In the meantime, we can try some of these options to get the correct env we want.

1. You can edit the name of GITHUB_TOKEN in .env file to something different and run op run --account=[account id] --env-file="./.env" -- printenv NEW-VAR-NAME
2. You can unset GITHUB_TOKEN, and add both GITHUB_TOKEN to .env file with different names, or you can create a new file with .env extension. Let us call it token2 as an example and put the old value there so when you need to run it, you can use op run --account=[account id] --env-file="./token2.env" -- printenv GITHUB_TOKEN

Best regards,
Nhat Nguyen.

thanks, I've unset the shell one for now as it's a very limited scope token and only used rarely by a few of my dev tools

I can reproduce this on v2.19.0

Might it be worthwhile to note this as a known issue in the docs (website or op run --help) since they both https://developer.1password.com/docs/cli/reference/commands/run/#duplicate-environment-variables that .env takes precedence?