We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
/usr/bin/eyaml
eyaml.pp
/usr/bin/puppet/eyaml
I'd suggest one or both of the following options:
params.pp
/usr/bin
$cmdpath
init.pp
The text was updated successfully, but these errors were encountered:
I got hit by this as well. Please merge the pull-request by benjamink :-)
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
When not using PE, the gem gets installed by default (in CentOS 6) to
/usr/bin/eyaml
, but theeyaml.pp
looks for the gem in/usr/bin/puppet/eyaml
.I'd suggest one or both of the following options:
params.pp
to/usr/bin
for$cmdpath
$cmdpath
as a class parameter ininit.pp
(the public entry point)The text was updated successfully, but these errors were encountered: