Rolling provisioning'a on a bare system?

Question

linux

Hey!
Sorry for a possibly stupid question.
I have a task - a linux system in an image (in the form of a box for vagrant). I want to automatically roll various software there, after raising it. It is known that this is done using shell scripts, as well as wonderful provisioning tools like puppet (chef, etc.). All this can be pushed into the process of raising the system with vagrant.
The last (puppet) I would like to use. But here's what confuses me. The software that I want to install on my system is not in the standard repository.
Let's take redis as an example, and the centos axis and look at the proposed modules for puppet. We will see that the module is offered to be installed.
Here my question arises - if puppet is what installs software on the system, why does it require manual installation of some modules (we don’t consider when puppet works without master-> slave)? I'm not talking about the fact that he himself should, as it were, be installed, i.e. for some reason, some script is not offered that can be executed on any system like install_puppet.sh, from the puppet developers?
Well, to solve the issues of managing third-party modules by puppet itself for their project, some people, as I found, wrote github.com/rodjek/librarian-puppet (it really needs to be installed separately somehow, and if vagrant starts c win machines, then you get that with this you fly, because it is put through a gem?).
The question is, why do so many things need to be installed in order to “automatically” install software on the system? With such squats, that the shell script, that the puppet look the same ...
Or am I doing something wrong?

Answer 1

An example script for provisioning pappet on a clean system: pastie.org/private/t5zklrl5uoalgccp4mtbla (line 21, attention). It remains only to confirm the certificate on the pappetmaster and that's it.