Bulk edit environment variables
complete
Anurag Goel
It would be nice to be able to edit environment variables in bulk. I often have the key/value pairs already somewhere else, but then manually re-entering them into Render can be a hassle. I'm imagining a 'bulk editing mode' where it just shows you one big textarea with all the ENV vars like so:
FOO_BAR=123
STRIPE_SECRET=4092142
When you save it, it just parses that for you into separate env vars. It would be really nice for power users.
Log In
A
Alex Bi
complete
A
Alex Bi
open
R
Reilly Sweetland
Idea for simple workaround: Support multi-line paste. Attached gif shows how Vercel does it. That would solve my problem, save loads of time and require minimal changes on Render's end.
D
Dan Croak
Related: I am migrating an app from Heroku. It has 20+ variables. After I've added them into Render, I realized it might be nice to extract groups of them into Render environment groups.
I created the groups, and then linked them to the service. Temporarily, I had duplicate env variables listed but quickly deleted the original ones. I had auto-deploy on at the time so a bunch of events were created and cancelled until I was done.
No particular harm done but:
* It would be nice to sort the environment groups alphabetically
* Should I have disabled auto-deploy before starting? Or maybe it would be unnecessary if there was a bulk edit
* Is there some atomic action that the UI can provide to let me link an env group while removing old env vars?
* Could the UI tell me when I've defined duplicate env vars across env vars and linked env vars? In this case, which one takes precedence? Should I be prevented from creating duplicates?
J
JP
+1 to this. This especially makes migration from heroku easier and less error prone... you can use
heroku config:pull --app xxxxxx -f xxxxxxx.txt
to download them, then copy/paste all at once!K
Kai Marshland
It would also be nice if it could support .yml files, eg FOO_BAR: 123