+1 on this... otherwise, the thing I'd like to do is for a set of config variables to be able to have an affinity to a version of my application.
The idea here is that as you develop your applicatioh, your configs will evolve (sometimes adding, renaming, or removing config keys), so a deployment that works on version "n" of your app might not really be compatible with version "n+1" (or "n-1").
I'm currently exploring this concept right now in my own work, so I don't yet have a real recommendation on HOW this needs to work, but the concepts are discussed in Chapter 2 of Continuous Delivery.
James Nail
supported this idea
·
+1 on this... otherwise, the thing I'd like to do is for a set of config variables to be able to have an affinity to a version of my application.
The idea here is that as you develop your applicatioh, your configs will evolve (sometimes adding, renaming, or removing config keys), so a deployment that works on version "n" of your app might not really be compatible with version "n+1" (or "n-1").
I'm currently exploring this concept right now in my own work, so I don't yet have a real recommendation on HOW this needs to work, but the concepts are discussed in Chapter 2 of Continuous Delivery.