Variable Environment Confirmation

[m1nty]

Since a variable can be uploaded in different environments, it's possible a developer may forget where each one is being used. For example, a variable could be uploaded in the Staging Environment, but could potentially be forgotten about when pushing to Production, which would result in some sort of error since the Production Variable would not exist.

A solution could be that a list of affected environment variables can be returned where the developer would need to confirm that the environments are correct.

[gagoar]

I get the confirmation. but what I don't get is when this happens. when the user does alo set VARIABLE VALUE ?

[m1nty]

Maybe when a variable is specifically set to local and not production environment? Or maybe neat time when the confirmation appears, is when you push something to git that used alo? That way it can be a good reminder before merging to master?