:modulepath: in config/settings.yaml seems to be ignored
rake puppet:import:puppet_classes wasn't finding my classes, so I added a couple of puts to app/models/environment.rb to show what environment and modulepath it's looking. Now, even though my settings.rb says
--- :modulepath: /Users/eric/Sandbox/svn/puppet/etc/modules/ :tftppath: tftp/
This is what comes out:
rake puppet:import:puppet_classes RAILS_ENV=production (in /Users/eric/Sandbox/foreman) using environment production scanning modulepath /Users/eric/.puppet/modules scanning modulepath /usr/share/puppet/modules Environment old:1 current:1 PuppetClasses old:0 current:0
I was able to trick it with a symlink but this would be good to have working.
#1 Updated by Ohad Levy over 13 years ago
- Category set to Importers
- Status changed from New to Assigned
- Assignee set to Ohad Levy
- Target version set to 0.1-1
The modulepath variable is not being used for importing classes, since the idea is that you should be able to read it from puppet.conf (if puppet can find it, we should be able to find it too ;))
It shouldnt be a big problem to make it work, but I was just wondering why it didnt pick up the right settings from your puppet.conf.
Can you post your puppet.conf?
#2 Updated by Ohad Levy over 13 years ago
- Status changed from Assigned to Ready For Testing
- % Done changed from 0 to 100
Applied in changeset 379d45b76c0f0c81e84fab692f9d75f43e95f41e.
#3 Updated by Ohad Levy over 13 years ago
- Status changed from Ready For Testing to Closed
#4 Updated by The Foreman Bot almost 2 years ago
- Pull request https://github.com/theforeman/hammer-cli-foreman-puppet/pull/27 added
#5 Updated by Ondřej Ezr over 1 year ago
- Pull request deleted (
fixes #21: this adds support from module path under the setting file and provides a fallback to /etc/puppet/modules