Couple of things that are still on my mind:
- Talked with @magnus and @ananace about their Pulp3 setup, which they manage solely by Puppet (no Katello) and while not interesting as such for us they have patches against
puppet-pulpcoreto enable repository management using Puppet which we could use in our CI forpuppet-pulpcoreandpulpcore-packaging - We have to improve our reporting when it comes to template updates. This was already in my head via the discussion in Add message about cloning templates by AkshayGadhaveRH · Pull Request #2697 · theforeman/foreman-documentation · GitHub, but then when talking to @ananace about a custom plugin they have for enhancing template sync tasks I realized we need this “even more” (the current reporting when syncing is “we synced N templates” and because the timestamps changed, they are all listed as updated).
- There is a new tool in the Ansible ecosystem: GitHub - ansible/ansible-creator: The fastest way to generate all your ansible content! - the diea is to provide a central place for scafolding various Ansible contents and especially also support generation of modules for APIs (something that @x9c4 and I talked about in the Ansible room: Generating Ansible modules for REST APIs without AI :: Config Management Camp 2024 Ghent :: pretalx). While this is not implemented yet, I really hope this will lower the burden of creating new modules and updating them, when we create/update API endpoints.
- I really enjoyed @Bernhard_Suttner’s idea of integrating security scanners into Foreman. Today we have OpenSCAP, but with some work we could extend this to others and benefit from different requirements different users might have. There is some further discussion in Process REX output about the technical side of things.