We should talk about/explore a logic path that allows the user to carry over existing environment variables in the latest revision when deploying a new update. Currently, "skip for now" would reset the next revision's environment variables even if some had previously existed.
See this for more context.
We should talk about/explore a logic path that allows the user to carry over existing environment variables in the latest revision when deploying a new update. Currently, "skip for now" would reset the next revision's environment variables even if some had previously existed.
See this for more context.