Foreman » Smart Proxy

Hello,

We use puppet dynamic environments in our platform to make changes without effecting the entire platform.

We put our 'shared/common' modules in /etc/puppet/modules and copies of some of these modules inside the environment to do dev/test.

Looking at the Foreman code for dynamic envs it should do the following, look in /etc/puppet/environments/$environment/modules add all classes then look in /etc/puppet/modules and add any additional classes. What appears to happen is it only looks in /etc/puppet/environments/$environment/modules and ignores /etc/puppet/modules

Dynamic set:
[master] # Dynamic environments
modulepath = /etc/puppet/environments/$environment/modules:/etc/puppet/modules

If we use static envs as below it appears to work as expected and pull classes from both paths.

[dev]
modulepath = /etc/puppet/environments/dev/modules:/etc/puppet/modules

-

This is currently causing us major issues as foreman is removing classes what the puppetmaster would accept believing they do not existing in the dynamic env.

ii foreman 1.4.0-1 amd64 Systems management web interface
ii foreman-proxy 1.4.0-1 all RESTful proxies for DNS, DHCP, TFTP, and Puppet