As I ran into this I assume this is an unintended side effect of the nesting of groups I think this feature would be handy.

The issue lays there in that one can not call classes out of other pupept environments, yet foreman allows one to built it that way. one could ofcourse reconfigure puppet to include a common modules patch in the configuration, but in some cases this is not possible or even wanted.

So what I would liek to see is the possibility to either define the shared module folder on puppet or set a host group to not allow nested environments. Or maybe even a step further let the foreman proxy lready identify common and exclusive module paths when it reads the puppet config and set a flag in the UI allowing and disallowing the nesting of the associated environments or classes. I would expect this to make the parsing during an import take longer but in essence foreman already reads the classes for each environment and it associated config/varialbles etc.