Unable to replicate.

puppet.conf:

[main]
environments=production,testing

[production]
manifest=/etc/puppet/env/production/site.pp
modulepath=/etc/puppet/env/production/modules

[puppetd]
environment=production

tests (gsub is a parser function provided by DavidS' common module):

root@junglist (branch: master) /etc/puppet/env/production# cat site.pp
node junglist {
   $ifs = gsub(split($interfaces, " "), "(.+)", "if_\\1")
   notify {
      $ifs:
   }
}
root@junglist (branch: master) /etc/puppet/env/production# puppetd --test --environment production
info: Loading fact configured_ntp_servers
info: Loading fact netmask
info: Loading fact acpi_available
info: Loading fact interfaces
info: Retrieving plugins
notice: Ignoring cache
info: Caching catalog at /var/lib/puppet/state/localconfig.yaml
notice: Starting catalog run
notice: if_eth0,eth0:0,eth0:1,eth0:2,eth0:3,eth1
notice: Finished catalog run in 1.08 seconds

Please provide more details, with specific replication steps if possible.

I’d go so far as to say that the workaround below is sufficient, and I’m not familiar enough with the underlying substructures to actually implement the work suggested by Luke, as such, here you go community!

Replying to [comment:7 DavidS]:

After a bit debugging with immerda, we found out that setting an additional global modulepath at least lets the puppetmaster work with those functions, even when using environments.

I’m running with this configuration already for quite a while and ahd no unexpected problems with it:

[main]
environment=production


Default modulepath without environments

modulepath=/srv/puppet/modules:/etc/puppet/modules:/usr/share/puppet/modules

[production]
modulepath=/srv/puppet/modules:/etc/puppet/modules:/usr/share/puppet/modules

[development]
modulepath=/srv/puppet/modules-development:/etc/puppet/modules:/usr/share/puppet/modules

I’m bumping this to the next release, because it’s too much work for not enough reward, at this point. I’ve increased the priority, since it is important.

so it wasn’t clear from reading this ticket, but I just did some tests on 0.24.6, and plugins in modules don’t work with environments.

The default modulepath is used for the plugin mount source, not the environment one.

This kind of defeats the point of plugins in modules if you’re using environments.

I took a crack at this and found that it’s totally dependent on #3015 – once that’s merged into master, I’ll try again.

I’ve pushed an incomplete version of this.

My code moves all of the scope functions into modules, but doesn’t successfully support environments – Markus will fix that.

The problem is that we have no real way of knowing which environment a given function is for; this problem also needs to be solved for the internal dsl work.

Pushed in ccc869ea48397235d7ba2a5695424eee4923cb9d to master.