A more general blocker is that some acceptance tests are red because of dependencies. The beaker-puppet install helper only works if all dependencies allow the latest version so all modules need to allow stdlib 5.0.0. This means I need to do releases of our modules. Given we’re getting close to the 1.20 branching I want to use it as an excuse for major version bumps which are always more invasive.
The first simple and fully compatible PR was just merged.
My next step is to change the certs module to always allow using a tarball (Refactor #24947: Move tar file parameter to puppet-certs module - Katello - Foreman). That should be a standalone change. We can probably bikeshed over the parameter naming so please have a look there. For actual testing I need to rebuild the RPMs with the latest changes. I don’t remember if I actually got the tests to pass. My testing setup for this is at home and it looks like I didn’t git push it. This is at a point where testing can be done and I’ll write up instructions.
When that’s merged, the next step is to finish https://github.com/theforeman/puppet-certs/pull/210. I just updated it to show the general direction I want it to go to, but I’ll need to do some actual tests to finish it. It can probably even be done in parallel to the above.
With those cert changes I think we can generate certs for any server type of server. We’ll still need some “manual” transfer of the tarballs.
Once those are merged, I’m going to rebase https://github.com/theforeman/puppet-katello/pull/209 and https://github.com/theforeman/puppet-foreman_proxy_content/pull/136. With those pieces in place I believe we can do split installations.
This is my current planning and I’d welcome help. Do note that I’m balancing quite a few issues and will need to set priorities. Given the 1.20 branching is coming up I don’t expect everything it to make it in time but we’ll see where it lands.