The idea
Configuration drift becomes difficult to explain when settings change without a record of purpose. A useful history connects each significant version to the problem it addressed and the evidence that justified it. It should also identify which version is active now.
Design choice
Preserve a known previous version before a risky change and define the rollback condition. Avoid leaving several similarly named files that all appear current. Historical records should be clearly distinguished from the active operational path.
Worked example
A deployment records the active configuration checksum and a brief reason for change. A later investigation can verify whether the running file still matches the accepted version.
Before you ship
- Identify the active version unambiguously
- Record the reason and verification
- Define rollback conditions
Examples are illustrative. Adapt the checks to your own environment.