Jira (FACT-1276) Module level external facts not resolved when using the Vagrant Puppet provider

[Michael Smith (JIRA)]

Title: Message Title

Michael Smith commented on FACT-1276   Re: Module level external facts not resolved when using the Vagrant Puppet provider Setup a Windows Vagrant system using the Puppet provisioner - I ended up using directory environments: config.vm.provision "puppet" do |puppet| puppet.environment_path = 'environments' puppet.environment = 'production' end environments └── production ├── manifests │   └── setup.pp └── modules └── foo └── facts.d ├── alpha.ps1 └── facts.yaml   5 directories, 3 files and installed a nightly build with this fix. Repeating Vagrant provision appears to work $ vagrant provision ==> default: Running provisioner: puppet... ==> default: Running Puppet with environment production... ==> default: Notice: Scope(Class[main]): baz ==> default: Notice: Scope(Class[main]): alpha ==> default: Notice: Compiled catalog for win-e5k8tm30719.localdomain in environment production in 0.05 seconds ==> default: Notice: Applied catalog in 0.01 seconds Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.