You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I'm trying to say is that adding support for stage specific environment variables shouldn't affect precedence at all and is not a question that needs to be asked. I assume there currently already is a precedence implemented (I haven't used up env) which would just stay exactly as is. Otherwise you'd weirdly interleave up env and up.json.
Currently you can't define these per-stage, only with
up env ...
. Ideally you can define them in the stage, and at the root level and they merge.I'm not sure if precedence should be given to
up env
's, or the up.json but probably the up.json would be the most clear?The text was updated successfully, but these errors were encountered: