No clear way to ensure module-data is loaded for (e.g.) puppet-boxen

[donaldguy]

I am trying to update boxen/puppet-zookeeper's tests to use newer (ideally Yoesmite-compatible) versions of various packages but it is choking if puppet-boxen goes beyond 3.4 when @ripienaar's ripienaar/puppet-module-data was introduced.

Since April 2014, the fixtures have loaded a newer than 3.4 puppet-boxen in the puppet-template, so I suspect this is affecting/will affect more people in the future (hence why I opened boxen/puppet-template#27 )

I see that @dgoodlad managed to get boxen/puppet-boxen@9339e55 to work but my attempts at following his lead have not worked out.

I added

Puppet::Util::Log.level = :debug
Puppet::Util::Log.newdestination(:console)

to @mattheath's zookeeper_spec.rb after updating spec/fixtures/Puppetfile to

mod 'module-data', '0.0.1',  :github_tarball => 'ripienaar/puppet-module-data'
mod 'boxen',       '3.6.1', :github_tarball => 'boxen/puppet-boxen'
mod 'homebrew',    '1.9.5', :github_tarball => 'boxen/puppet-homebrew'
mod 'stdlib',      '4.1.0', :github_tarball => 'puppetlabs/puppetlabs-stdlib'

and Gemfile to

source "https://rubygems.org"

gem "cardboard", "~> 2.1"

and adding

$: << File.join(fixture_path, 'modules/module-data/lib')

to spec_helper.rb

but the output is still as shown in this gist
https://gist.github.com/donaldguy/f0bbaa2afeddc9bcbe79

Which has a lot of spew about failed hiera lookups and notably no sign of the debug messages about the module data backend like
https://github.com/ripienaar/puppet-module-data/blob/0cddf7a3dbcdf8a5ead845ad29caf54ac76b1bfa/lib/hiera/backend/module_data_backend.rb#L8
would suggest should appear

so... I'm kinda stuck. Is there some other way rspec-puppet needs to be cajigored?

[n0ts]

puppet-module-data does not work Puppet 4. Puppet 3 is EOL this year, Thanks.
@jacobbednarz Could you close it? Thanks.