New Variable type that is never part of a release snapshot
In very rare cases, some variables need to be updatable and apply to previous releases without having to 'update all variables'.
A specific example: A server needs to move IP address, and the previous one decommissioned. In all releases it needs to know the IP address is different, but also a variable has changed and only relates to the new code, ad a new one added also relating to later releases. 'Updating all' variables would not work for the release.
If there was a special global variable area either for projects or like a set where you can change it and it does not get snap shotted - this would solve these rare edge cases for variables needing to change for all releases
Vanessa Love
shared this idea
-
John Grandy
commented
What's the latest on this ?
-
Anonymous
commented
This should already be a thing. Perhaps you could tick a box next to a variable which decides whether it's snapshotted or just latest version.
-
Tim Walker
commented
This is so crucially needed.
We have a lot of projects for different IIS applications that all utilise different usernames and passwords for SQL connections that get updated inside their respective configs.
When a password is updated and sometime later an old release is deployed...unsurprisingly the application breaks !!!
-
James Murphy
commented
I can think of a dozen other examples for this: URLs for other systems (like TFS or TeamCity), e-mail notification lists, new API keys, etc.