puppet - module/class - using - apt/packages -- 2

I like to use puppet for managing existing hosts. Hosts are running Debian 10 (bare-metal, VMs running on VMWare ESXi, GCP, ...) I describe now what I normally install to get an understanding what I like to have replicated with puppet. The following lists packages getting installed using apt-get install apt-file bc bzip2 ca-certificates csh debian-goodies dialog dnsutils dos2unix exim4 ftp gcc git gnupg ifupdown iproute isc-dhcp-client joe jq less locales lsb-release lsof lynx make mc mime-construct needrestart net-tools netbase netcat ntp openssh-server pwgen rsync screen sharutils software-properties-common stress subversion sudo sysstat tidy tofrodos unzip vim wdiff wget whois linux-headers-$(uname -r) rar which needs /etc/apt/[login to view URL] to hold "non-free" additionally I install these software solutions regularly - Google Cloud SDK based on [login to view URL] - Docker-CE based on [login to view URL] For UI Systems I sometimes install things like those Chrome based on [login to view URL] wget -q -O - [login to view URL] | apt-key add - echo "deb [login to view URL] stable main" | tee /etc/apt/sources.list.d/[login to view URL] apt update && apt install google-chrome-stable google-chrome-beta Sublime based on [login to view URL] wget -qO - [login to view URL] | sudo apt-key add - sudo apt-get install apt-transport-https echo "deb [login to view URL] apt/stable/" | sudo tee /etc/apt/sources.list.d/[login to view URL] apt update && apt install sublime-text DBeaver [login to view URL] dpkg -i [login to view URL] DBeaver does not have a repo, therefore having a module/class in place which has a the [login to view URL] on the server and then rolled it out and installed on the nodes I have normally a simple crontab in place: crontab -l TERM=linux MAILTO="target\@[login to view URL]" 00 04 * * * /bin/bash /opt/[login to view URL] Now to what I like to have: I have started testing things out and know that you can manually install packages like ntp or you utilize [login to view URL] and use foundations that are better than what you construct yourself. Currently I test puppet on a LXC environment, 1 server node and 2 agent nodes. For easy all settings are going to be installed on both agents, so no grouping is needed. I have a small set of a vanilla /etc/puppetlabs/code directory and this can be used to see where I am at and as a starting point. I like that apt is maintained using [login to view URL] as a foundation so that the package have a good foundation. I like that the above packages are installed either the way similar to using prefined packages like [login to view URL] or if there is no solution from puppetlabs then the package should be installed using [login to view URL] The additional packages above like Google Cloud SDK which have their own repo, the repo should be handed using [login to view URL] For docker [login to view URL] For apache [login to view URL] Puppet_Agent should be managed via [login to view URL] My crontab example should use [login to view URL] The Server and Agents were installed a vanilla approach: Server/Agent: wget [login to view URL] dpkg -i [login to view URL] apt install puppetserver apt install puppet-agent # Agentn -On my system I have installed: puppet module install puppetlabs-ntp puppet module install puppetlabs-apt The solution should be based on my /etc/puppetlabs/code supplied as [login to view URL]