Puppet VS Ansible

I will happily direct your attention here: https://github.com/puppetlabs/puppet

We started by decoupling Puppet from Facter as much as we could, introducing the possibility of having multiple Facter backends. While Puppet would use the default Facter implementation when running on its own, external users would be able to define and pass their own Facter implementation when initializing Puppet, similar to how puppetserver configures Puppet to use its JRuby-compliant HTTP client.

I would recommend that you familiarise yourself with tools like Ansible. On the one hand, this makes many processes easier and on the other hand, such knowledge is often required by the employer.

As a sidenote: automate all the things

We hope these changes help you navigate the Ansible documentation more easily and find the content you're looking for. More changes to the User Guide are in plan and next up we're aiming to consolidate some of the Playbook content in the User Guide. You can find out more about this effort, and join in the conversation, in GitHub issue 78082.

It was recommended by a colleague that i might enjoy delving a bit into Ansible and suggested i check out the Complete DevOps Ansible Automation Training instructed by Imran Afzal. I can already see why this course was recommended, the instructor is very knowledgeable and easy to follow.

Improve Ansible performance https://github.com/ansible/ansible/issues/76380

You should engage a DevOps service provider with at least five years of expertise with automation technologies such as Puppet, Ansible, Chef, and SaltStack, as well as a high degree of skill with Python, Ruby, PHP, and Java. Additionally, they should be acquainted with continuous integration platforms such as Jenkins, CruiseControl, and CruiseCrontrol.NET, to mention a few. Additionally, it will be of great assistance if they have expertise in delivering code, database administration, system design, and software architecture.

Make ansible playbooks to set up your environment. You should be able to get applications/configuration/dotfiles set up using one ansible invocation, then you just need to worry about recovering data. But data you can download from the cloud as you need it.

A shell script could work, but the best option is to use an orchestration/automation tool like Ansible, Chef, Puppet, or Salt. Using these tools you can define the steps needed to set up your project in a set of files, and just by invoking vagrant provision the VM will be set up. The advantage is that setting up a new development environment with this method is easy, fast, and can be shared with all the members of the project.

That should answer your golang question, but if not convinced, we even have a golang module in our tests to ensure this works. https://github.com/ansible/ansible/blob/devel/test/integration/targets/binary_modules/library/helloworld.go