Replies: 1 comment 4 replies
-
Hi @henderea We made some changes to Environment Variables. Let me know if this solves your use case https://vercel.com/changelog/environments-variables-per-git-branch |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When adding a system environment variable at command line, setting the name of the environment variable to the name of a system environment variable value option should automatically select the referenced system environment variable.
For example, if I run
vercel env add system VERCEL_URL production
, I shouldn't have to answer any prompts, because I'm clearly referring to theVERCEL_URL
system environment variable. If you don't want to force the assumption, you could ask a yes/no question "Use the system value VERCEL_URL?" and have a--yes
or--confirm
flag for the command so I can skip the prompt.Alternatively, allow me to specify the system environment variable as part of the command, such as
vercel env add system VERCEL_URL production --value=VERCEL_URL
orvercel env add system VERCEL_URL=VERCEL_URL production
or some other style.Lately, vercel has been getting more and more inconvenient. I used to be able to specify everything in a JSON file and deploy with a single command. If you're not going to bring that back, at least make the CLI more compatible with scripting so I can automate some of my default setup.
Beta Was this translation helpful? Give feedback.
All reactions