puppet_trocla.git - [puppet

Age	Commit message (Collapse)	Author
2016-06-07	keep trocla object around - addresses #18	mh
	Per puppet function call we now created a new Trocla object. This is a) a very naive approach and b) obviously can lead to a lot of inefficiency as we for example need to build up trocla each time again. Also this means that we are running into problems like opening a connection to a database system each time a trocla lookup is done (and we never close the connection :-/). The proper way to solve this is to make sure we don't create too many trocla objects. With this change, we should now create once a global trocla object PER puppet(-master/-server) process and keep it around for the life time of such a process.
2015-08-12	whitespace cleanup	mh

2013-02-28	Removing calls to Puppet.features.rubygems?	Michael Franz Aigner
	This makes the Gem usable in the latest Puppet versions. The handling of RubyGems got revised in Puppet 3.0.1-rc1: http://projects.puppetlabs.com/issues/16757 The new policy is that either bundler and/or rubygems are guaranteed to be loaded and initialized when the Puppet manifest is evaluated, making it unnecessary for Puppet modules to load rubygems. This new policy broke the puppet-trocla module. This is because 'Puppet.features.rubygems?' always evaluates to false now, which causes the module to abort the manifest compilation with a message informing about the necessity of RubyGems to be present.
2011-10-27	merge	mh

2011-09-06	as setting a hash first is a bit cumbersome, we provide the possibility to ↵	mh
	pass a yaml string
2011-08-08	wording	mh

2011-07-27	bring config filename in line with what trocla uses	mh

2011-07-27	init of trocla module	mh