Ansible tips&tricks
In these pages you will find much of the documentation that I collected over the years. This is by no means a "We say so" document.
I have worked in a number of organizations implementing ansible and automation platform, under control of "configuration As Code".
This is my personal view on "How I would do this".
This site is still a work in progress, check us regularly for updates.. The code is changing as ansible and automation platform changes.
As time passes and things get updated with new versions (Automation platform for example..), I will update the things I'm using actively. All others will get outdated and finally archived. In these older chapters you can find some historic code samples that might interest you, this is why they still exists.
26-08-2026
Updated to the new patch release (v2.7-6) by deleting and fully reinstalling containerized automation platform.
After installation ran all configuration as code to reinstate the full configuration to the point
before the deletion. Using the code described in this site.
Some statistics:
- 7 organizations
- 8 custom EE's (hosted in a separate registry)
- 6 custom collections (rebuild and load)
- 48 projects
- 58 job templates
- 2 workflows
This took just 40 minutes using the recovery as described here..
I'd call this successfull..
Taking the rebuild of the execution environments and collections out of the recovery process has some advantages:
- better version management in separate registry for execution environments
- better version control for collections using a separate host for storage
- recovery process has less steps and is much simpler.
Yust writing all knowledge down helps me to burn it into my braincells.
I hope you enjoy this as much as I did writing and learning it.
Enjoy..
<== Use the left side menu to navigate the documentation
Ansible is constantly changing and as my focus is on configuration as code, I will update this constantly, with this exception:
When a new version is released of ansible automation platform, the previous version will no longer be updated, the focus shifts towards
the new version. So in following the itterations in versions of the Ansible Automation Platform, you can follow the evolution of the code
created to run configuration as code.
I will try to update the code as soon as possible when running into things that are not working as planned.
This means there might be errors, when found I'll update the configuration, so when running into an error, check the config again, or leave
a comment and I will try to fix it.
This way you can help me and others in the community....
This site is (since 01-01-2026), hosted on virtual machines, created with ansible code, running on automation platform. The site is now
running on 3 linux containers(LXC on proxmox) with nginx, load balanced in a pool through a nginx proxy.
The whole setup is created using ansible and the site is deployed through a gitlab pipeline. The pipeline uses shortlived certificates to copy
the new content to the webservers, no users ever login to the webservers.
All in line with the automation principles.
The playbooks used for this installation, will be added later.