Shared and manage environment variables and secrets #633
Replies: 9 comments 3 replies
-
|
Direnv is another tool that does this. |
Beta Was this translation helpful? Give feedback.
-
Seconded. I'd favor a portable solution over something specific to my terminal (emulator) any day. |
Beta Was this translation helpful? Give feedback.
-
|
@reitzig direnv, is a shell tool. by portable do you mean across OSs or across shells, ...? The plan is to build Warp for Mac, web (wasm), linux, and windows. |
Beta Was this translation helpful? Give feedback.
-
|
Portable across terminals; my colleagues might not use Warp even if I did and agreeing on a "background" tool is a lot easier than a "frontend" tool. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
From @rkabrick via Discord:
|
Beta Was this translation helpful? Give feedback.
-
|
from @gagata via discord
|
Beta Was this translation helpful? Give feedback.
-
|
From brick via discord:
|
Beta Was this translation helpful? Give feedback.
-
|
I would probably choose 1password plugin for warp, instead of warp offering me their custom stuff. Why? I dont want a terminal managing my secret. :P |
Beta Was this translation helpful? Give feedback.
-
|
regarding env variables, I may agree for local development environment, but for secrets I do not. |
Beta Was this translation helpful? Give feedback.
-
|
The project-level stuff is quite cool (deserves a separate thread maybe?), but it I dislike the environment idea, especially because it feels pretty one-dimensional. Imagine projects with multiple environment requirements for development (a la profiles). You would then need a way to discern between them at Warp level (or you'd ignore the profiles, which is what always happens and everyone's wallowing in a sad half-solution). Also, depending on how this is implemented (from a workflow level), you can have an increasingly divergent workflow between yourself and colleagues, etc. This is something others have already expressed concerns with. What might be cool instead is having a way to better integrate with the shell and the environment/tooling... Someone mentioned direnv earlier. An example of this could be to respond to the value within the environment. Eg, if Basically, the whole of my post can be summarised as "augment what's there, don't replace it", which feels like what Warp has done so far. I mostly because replacing what's there in this case comes with an unimaginable scope creep, and then suddenly they become an all-or-nothing thing, mixed in with the sunk-cost fallacy, this becomes a great recipe for half-baked cult features (by cult features I mean something like a "cult fan"; it's absolutely adored by a small niche, but much less useful in the "real world") |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
Provisioning a project with the right environment variables is often very difficult. It's unclear which tools or scripts need to be run and what dependencies I need.
Describe the solution you'd like
I'd like for Warp to automatically embed shared env vars and secrets when I
cdinto the appropriate directory.Additional context
Technically, two possible ways we could implement this are by integrating with tools like Nix or Docker. We could also investigate building our own format for representing shared environment variables on a per directory/repo basis. Using our
precmd/preexechooks, we could source these environment variables as necessary.Beta Was this translation helpful? Give feedback.
All reactions