In this chapter we've introduced the example control repo and seen how to download it. We've explained the control repo pattern, and how it works with r10k and the Puppetfile to manage third-party and local modules. We've learned how to fork the repo and pull changes from upstream.
We've looked at the example role and profile classes, and seen how Puppet can use Hiera data to configure user accounts, SSH keys, allowed users, and sudoers privileges. We've covered the use of Forge modules to manage time zone setting and NTP synchronization. Additionally, we've explored the resources and scripts necessary to control automatic Puppet updates and runs.
The demo repo contains bootstrap scripts to help you put a freshly-provisioned node under Puppet control, and we've examined how these scripts work in detail.
Finally, we've learned how to adapt the demo repo for your own site, and outlined how to add your own users and access settings, and your own common profiles, and per-node role classes...