I know this question has been up for debate before, but I like to raise it again.
We have an operations department that are totally separated from the product/developemtn team (don’t get me started about how feel about this). This is creating some challenges when it comes to deployment processes and especially releases. The operations department have control over our staging and production environments, which mean that the product team does not handle variables specified for these environemnts, but we create releases (yes, I am part of the product/development team).
Some times the operations department might be weeks behind, and when that happens, global variables shared between projects might have changed (the product teams are very agile and can create several releases per day and constantly evolving the applications). In this case, updating variables for a former release might screw up that release because it will get the updated global variables that are NOT compatible with that specific release. See the problem?
Therefor it would be terrific if one could update a specific variable instead of all of them.
I know, I know, the main problem lays in the organization layout. This would not be a problem if we were a cross funtional team spanning through all of the parts of the development process. However, sometimes it takes time to convince old companies to reorganize into something better.