Practice: Version Control Your Configuration

[TristanBarrow]

No description provided.

[dcmoore]

When I went to go link this to its capabilities, it seems we have an old version of this practice already. See: Separate Config from Code. There are important ideas covered here that aren't articulated as clearly in the old version. For this PR, can you update the existing practice page with the content and ideas in this one?

[TristanBarrow]

Porting conversation from slack:

Tristan:

I see "Separate Config from Code" as distinct from "Store Configuration in its Own Repository".

To me, "Separate Config from Code" is something pretty much everyone needs to do regardless of situation.

"Store Configuration in its Own Repository" is sometimes not what we want to do. If the customer is using a vault of some sort, I don't think we should push them to use a repo instead. There is not a problem with using a vault to me.

"Store Configuration in its Own Repository" is an implementation of "Separate Config from Code" but they are not equivalent.

Dave:

I think you've got a good point there. Perhaps there's a better way to name the two in order to better illustrate the difference.

[TristanBarrow]

I opted for "Version Control Your Configuration" and "Decouple Configuration from Code".