Puppet provisioner not working with ripienaar/puppet-module-data

[Fraser Goffin]

For some time I have been using the excellent ripienaar/puppet-module-data module. This provides a very familiar way to use Hiera but at the individual module level.

I have recently upgrade to Puppet v4 and this module still works successfully when run with 'puppet apply' (I am using masterless puppet).

It also works successfully if I use the Vagrant shell provisioner with an inline 'puppet apply'

However, when using Vagrant (I'm using the latest 1.7.4 version) with the puppet provisioner, the module is NOT called (it 'injects' itself after traversing the site
level hierarchy), and therefore none of the Hiera values get resolved whether using automatic parameter binding or direct calls.

Given that this works happily outside of Vagrant, or indeed, inside a Vagrant image using puppet apply, and using the Shell provisioner, I am *assuming* (but I could be wrong) that the Vagrant puppet provisioner is where the issue is.

Can anyone shed any light on why this might be and, ideally, what could be done. I'm happy to help ?

I'm going to post the same question to the Puppet group since it's puppet related, so apologies in advance to anyone who uses both groups for the cross posting.

Kind Regards

Fraser.

[Fraser Goffin]

Forgot to mention above, I'm running Puppet v4.x on the VM.

[Fraser Goffin]

... and this was (and still) works successfully using Vagrant 1.7.2 and Puppet 3.x, but we need to move up to Puppet 4 and Vagrant 1.7.4 is the version that correctly supports the new features.