I’m currently working on the Foreman Salt plugin and I would like to discuss a possible improvement concerning the installation:
Right after the installation via
foreman-installer --enable-foreman-proxy-plugin-salt, a couple of steps have to be performed which add content to the
/etc/salt/master configuration. You can see them here in the plugin manual. I summarized these steps in an example configuration which you can find on GitHub here.
Most of the changes which are made manually by now are actually known in the
foreman-installer already. Therefore, I want to make the proposal of writing this configuration file as
/etc/salt/master.d/foreman.conf.example during the plugin installation. This would accelerate the installation process since the admin just has to check the
.example file and can start using it directly, if it seems alright for the setup. Moroever, it would minimize the plugin installation manual.
A disadvantage could be the growing complexity of
foreman-installer. So, I have a couple of questions:
- Is it appropriate to use the
foreman-installerfor writing/adding configurations like I want to?
- Is the
foreman-installerused to write configurations in
/etc/some_softwarealready? - do we have another plugin which does something similar?
- I believe, I would have to make changes to
puppet-foreman_proxy. Would you either:
- Ship some
- Ship it within
- Go a different way, I didn’t think of by now?
- Ship some
Looking forward to your feedback!