Although writing code directly to the disk on a Puppet Master is the easiest way to get started with Puppet, it is the least efficient model for managing infrastructure changes with Puppet. Manual changes leave the users to manage the following issues individually:
- Backup and recovery
- Change management
- Replication of Puppet Masters
- Replication of Puppet environments
Without code management, backups are often performed via disk snapshots, or by simply bundling code and moving it to a separate location in case of emergencies. Manual code placement leaves the organization responsible for maintaining a cadence and process for backing up and restoring, and for change management. Without any code management, replication of code to Puppet Masters and Puppet environments is a fully manual process, which leaves all Puppet code testing and implementation to dangerous...
