Okay, this is a bit more abstract than my usual support questions, so bear with me.
I’m evaluating Foreman in various potential roles at work, including the “all-in-one” kind of role. It would be great to have Foreman managing Puppet for us, and indeed that all actually works great. The major bug-bear I’ve discovered today, however, is that it takes between 12-15 minutes to import my full set of environments and classes (by pressing the “Import environments from hostname.someplace.com” button).
This isn’t an unreasonable amount of time - I would love if it was a lot faster, but considering it’s importing the entire set of branches it’s pretty good.
The problem that arises is that our workflow usually involves creating a new branch in the control-repo tied to the issue/project we’re trying to solve/work on. In order for me to enable this workflow, I would need to have the user create their branch and then go trigger an import. This is because in order for them to work on a test machine, they would need to assign that environment (and/or role) to a host or hostgroup.
Would it be possible to implement some sort of system where I can scan/import a single environment at a time? In that scenario, they can simply import the new branch they created, which should be very quick compared to scanning/importing 80+ environments with a few hundred classes!
Just thoughts for now, please let me know what you think.
One other enhancement I’d love to see - being able to add Puppet classes to a node or host group that Foreman isn’t yet aware of. This way I could create a new role and flesh it out and test it without needing to do a long full environment import. Then again, being able to import/update a single environment would make this unnecessary.
Foreman and Proxy versions:
Foreman and Proxy plugin versions:
Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)
Nothing relevant available yet