Variable value scoped to release version
Often times I need to update a configuration variable but, only once we are about to release a particular release.
For example, if I'm upgrading my SQL server and moving to a new machine. I've got a release for the new SQL server version let's call it 220.127.116.11, however, I can't put my new connection string variable into Octopus configuration because I'm still deploying version 1 releases until it's time to migrate.
What I would like to be able to do is specify that the variable for the connection string is X for all releases prior to v 18.104.22.168 and then the value changes to Y for releases 22.214.171.124 and above.
Tim Evers shared this idea