Use within Vagrant / Hiera

[Iristyle]

We're trying to use within Vagrant, and was hoping you could provide some additional documentation.

As you may know, Puppet is installed / run from the VM, and Vagrant has a mechanism for configuring modules, that may live on the local file system.

Basic mechanism (assuming you're in a working directory of modules that's relative to the Vagrantfile)

• Clone the source - git clone https://github.com/basho/puppet-riak.git
• Tell Vagrant / Puppet how to find the modules, with the following (or similar) in the Vagrantfile

Vagrant::Config.run do |config|
  config.vm.provision :puppet, :module_path => "modules"
end

Then of course it's on to using the riak class.

However, my concern is regarding the use of Hiera. We can clone the Hiera sources in the same way we do for the riak module to the modules directory via git clone -b 1.x https://github.com/puppetlabs/hiera-puppet.git.

This would be necessary for Puppet 2.x. For Puppet 3.x, Hiera is in the box from what I understand.

So I'm not sure if we need the mentioned Gem or not.. ??

In particular, this mention is from the docs

Make sure you are shipping the custom functions in this module to your i nodes, by setting pluginsync=true;

[main]
pluginsync = true

Requires that hiera-puppet gem is present.

Any advice / documentation is helpful here, before we go down a potentially painful road ;0

[haf]

As you say, the hiera gem is bundled with puppet nowadays, but wasn't before. The docs is a wiki; would you care to update to state that the hiera gem nor the pluginsync feature is required for Puppet 3.0?

[Iristyle]

OK -- so pluginsync is not required anymore then?

We're pretty new to Vagrant and Puppet, so wanted to make sure that we had our ducks in a row.

We can probably help out with some docs once we verify this locally.

[haf]

Yes, that's correct. It's now on by default. Closing issue - tell me if you fix the docs! :)