https://bugzilla.wikimedia.org/show_bug.cgi?id=67214
--- Comment #5 from Bryan Davis <[email protected]> --- (In reply to Tyler Romeo from comment #4) > Indeed, but there should probably be some sort of migration plan, > considering that the plugin currently relies on the import statement in > order to add roles. One way forward for this would be to shift to using the hiera_include() feature which allows a hierarchy of yaml and/or json configuration files to declare a list of puppet classes which should be applied to the active node. It will take some effort, but with the combination of well constructed modules and hiera's configuration selection mechanisms we should be able to eliminate "role" classes which seek to provide customization of more general features. It could be done in the most brutish manner today by moving the current roles collection to a module and turning the other non-module configuration into modules that can be discovered by the puppet autoloading mechanism. In my personal opinion, MediaWiki-Vagrant should seek to track the work in this direction that is currently in the planning stage for the operations/puppet.git repository with an optimistic long term goal of abandoning much of our custom puppet implementation for utilization of operations/puppet.git directly. We will probably end up with a few odds and ends which are MediaWiki-Vagrant specific, but hopefully by the time we get close to convergence we will also see a reasonable method to augment the base classes for our environment. The desire to unify production, beta and labs projects within operations/puppet.git gives me hope that we will have enough eyes and fingers dedicated to the task to make significant progress towards this ambitious goal. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
