[21] Conditionnal injection (jinja?)

Hi Emmanuel,

Thank you very much for writing such a detailed description!

We really like your idea of templating the .env file. We even have done a first step of that in the op inject command already: allowing variables in the reference, so you can use the same configuration for multiple different environments. You can find it described here: https://developer.1password.com/docs/cli/guides/config-files#step-4-differentiate-between-environments . We're planning on adding the same variable support to op run for environment files as well. How do you feel about that?

Regarding your use case of having a default configuration that's overloaded with values specific to a single environment, would a setup with multiple environment files, e.g. defaults.env and production.env work for you? When you pass multiple environment files to op run, variables defined in the second file take precedence over variables defined in the first file.


op run --dotenv-file defaults.env --dotenv-file production.env -- ./run-your-app


Would love to hear your thoughts and iterate on this further! Thank you so much for all your feedback so far! ❤️

Cheers,
Simon