Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
.env files should support more file formats
Hey, I was incredibly excited to see the 1Password beta supporting .env files. After testing it out in the latest beta, I understand that this is incredibly useful for environments that support trad...
1P_Phil
Moderator
ModeratorHi simonbs ,
Another great request, thank you for sharing this. It is helpful to know you are using 1Password in your development flow for iOS apps. I too used to develop iOS apps and can relate to your pain. From your note, it sounds like the request is to output different types of files that could be defined by a template and then the Environments feature would replace the secrets (like you mentioned like 'op inject' does from the command prompt).
Something like this:
1) Define a template file with 1Password URIs (could be swift, could be .env, or any other format, but basically a text file)
2) Create a new environment that knows about this template file (from #1) define the secrets linking to the URIs
3) Define a destination
4) Attempt to run a build process, that tries to access the destination from #2.
Let me know what you think.
Regards,
Phil & Team
I mean, right here you're hitting on my dream setup. The way that the "op run"-style .env works is really useful and infinitely flexible. The only downside is that your application suddenly needs to be aware of 1password and it ends up polluting up my run scripts and package.json, etc.
The dream setup is to use the "op run"-style template files (i.e. .env.ref) but instead of using op run or op inject, I want these to be picked up and populated using the new named pipe method that the new environments use.
It's the best of both worlds, flexible .env files fitting any template/format, and totally transparent to the end application.
