Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Path to eyaml gem binary is wrong #31

Closed
benjamink opened this issue Oct 24, 2014 · 1 comment · Fixed by #32
Closed

Path to eyaml gem binary is wrong #31

benjamink opened this issue Oct 24, 2014 · 1 comment · Fixed by #32

Comments

@benjamink
Copy link
Contributor

When not using PE, the gem gets installed by default (in CentOS 6) to /usr/bin/eyaml, but the eyaml.pp looks for the gem in /usr/bin/puppet/eyaml.

I'd suggest one or both of the following options:

  1. Change the default path in the params.pp to /usr/bin for $cmdpath
  2. Allow for setting the module's $cmdpath as a class parameter in init.pp (the public entry point)
@iverberk
Copy link

iverberk commented Nov 8, 2014

I got hit by this as well. Please merge the pull-request by benjamink :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants