Environments edited on-server source control


#1

I’m introducing an organization not used to IAC to Chef. My original plan is to use the standard tools such as source control, code review and continuous integration to ensure the code stays clean, but I’ve notice people can… and are… editing environments on the server.

So what can I do with this when it comes to source control? Do these get checked into an internal git repository or is the only way to deal with this have the CI server periodically do knife downloads of the environment files, check for changes and check in any manual edits?

What do other people do to combat this?

Thanks

Keef