I would be explicit about telling vagrant where your modules folder is.
e.g.
https://github.com/ferventcoder/vagrant-windows-puppet/blob/master/boxes/win2008r2x64-vagrant/Vagrantfile#L34
On Thu, Nov 21, 2013 at 12:16 AM, Roger Yu wrote:
> yes i installed vagrant windows version and use vagrant
yes i installed vagrant windows version and use vagrant provision command
to trigger puppet provisioner
and as I mentioned above, manifest file base-hadoop.pp works fine, just
init.pp under modules folder was not called
Rob Reynolds於 2013年11月19日星期二UTC-8上午9時08分24秒寫道：
>
> For vagrant, are you kic
For vagrant, are you kicking off the commands with the vagrant puppet
provisioner? And are you using vagrant-windows plugin?
On Tue, Nov 19, 2013 at 8:28 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> Hi,
>
> I haven't played with Vagrant, but your wording makes me ask:
>
> Is there
Hi,
I haven't played with Vagrant, but your wording makes me ask:
Is there indeed an agent (as in `puppet agent` as opposed to `puppet
apply`) at work? Because that will never use a manifest from your local
machine. Puppet agent has the sole purpose of connecting to a master.
Cheers,
Felix
On 1
Hi all,
I have been working on a configuration of a Masterless configuration on
Windows. I am able to get individual jobs to run like:
puppet apply
However, I would like to spin up the Vagrant box off a base VM, and have a
puppet manifest file in a location where puppet knows to look and pro
