I think this may be a good start and interim solution. But there are problems with our existing installer and even the puppet based approach that won’t go away with it.
- more complicated things will continue sufferring from installer CLI limitations (no webui wizards,
--help
showing too many things, no interaction between related parameters) - we need to own the whole configuration of deployed service (e.g. httpd, rsyslog, postgresql, redis) not just things we want to install (foreman, smart proxy, pulp, …)
- lack of devs willing to write the puppet code, resulting in rather building separate scripts or just documenting manual reconfiguration
Of course rewrite does not help with at least the first one. But as explained at RFC: Make Foreman easy to deploy and maintain this shouldn’t be a rewrite. We need to have the installer do the minimum and make the rest of the configuration from Foreman itself. But I agree, until we get there, existing installer can be used.