Issue #21576 has been updated by Hunter Haugen.

Well I think it is expected that `[master]` should apply to the `puppet 
master`, `[agent]` to `puppet agent`, and `[main]` to everything, so perhaps it 
would also be expected that a `[module]` section would apply to `puppet 
module`? (Though it does not, unfortunately.)

Per-face settings sections in `puppet.conf` do not seem to be supported, though 
it would be awesome if they were.

----------------------------------------
Bug #21576: puppet module list doesn't walk all of the modulepath directories
https://projects.puppetlabs.com/issues/21576#change-94061

* Author: Richard Pijnenburg
* Status: Unreviewed
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* Affected Puppet version: 
* Keywords: 
* Branch: 
----------------------------------------
When having multiple directories in the modulepath it doesn't process all of 
them.

in puppet.conf i have:
 

modulepath = 
$confdir/modules/library:$confdir/modules/shared:$confdir/modules/common:$confdir/modules/platforms/isp/modules:$confdir/modules/platforms/isp
 
When running 'puppet module list' i get:
<pre> 
[root@puppetmaster001 puppet]# puppet module list
/etc/puppet/modules
├── common (???)
├── library (???)
├── platforms (???)
└── shared (???)
</pre>
Only when specifying one of the dirs i see all the modules. ( although still 
with the ??? behind them )

Will take a stab at this and see if i can solve it.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to