Along with the conversion of katello-deploy to a more Foreman first and friendly repository, we also have:
1) a Katello devel installer scenario 2) puppet-katello_devel for configuration devel environments I think it would be beneficial to give these the same treatment and move them into the mainstream. The first step would be renaming and making any changes necessary to puppet-katello_devel. The second step would be adding a devel scenario to the foreman-installer or in a separate repository focused on that scenario. Naming ----------- Options for rename: 1) puppet-foreman_devel 2) puppet-forklift 3) puppet-forklift_devel 4) Other Code Updates -------------------- Besides renaming, we've been working to make some changes that provide a wider use case of the puppet module. The first is adding plugin support to allow generating a dev environment of your choosing or adding plugins configured properly after a base setup [1]. Similarly, taking the existing puppet-hammer_devel module and merging it in to provide a single cohesive module for development setup [2]. Are there other changes that devs would like to see ahead of time before convergence? [1] https://github.com/Katello/puppet-katello_devel/pull/71 [2] https://github.com/Katello/puppet-katello_devel/pull/77 -- Eric D. Helms Red Hat Engineering Ph.D. Student - North Carolina State University -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
