I'm using op run combined with a .env file to load our development configuration, but we have quite a bit of optional configuration. Some devs may need part of the config, other devs might need other parts. In order to make this simple, it would be nice if when using the op:// in an .env file with op run you could tell the command to ignore missing vaults or slots and just not set those environment variables, maybe printing a warning? Would be nice to do this reference by reference in the file so some could be required and other config optional, but a global flag on the op run command would be better than nothing here too. Bonus points for being able to specify a default value other than empty/not set for each environment variable reference in the .env file.
Using CLI version 2.6.2 and didn't see a way to do this, but maybe I'm missing something? Right now I just get
could not resolve item UUID if I have a slot that isn't in my vault
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided