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.

Sign up for GitHub

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

Jump to bottom

Can't use 'mco plugin package' when Puppet is installed via Gems #193

Closed
lukebigum opened this issue Aug 30, 2018 · 1 comment
Closed

Can't use 'mco plugin package' when Puppet is installed via Gems #193

lukebigum opened this issue Aug 30, 2018 · 1 comment
Labels
enhancement

Comments

@lukebigum
Copy link
Contributor

mco plugin package fails when Puppet is installed using Gems and Ruby Environments, because /opt/puppetlabs is hard coded in aiomodulepackage_packager.rb .

Patch coming very shortly.
lukebigum added a commit to lukebigum/puppet-mcollective that referenced this issue Aug 30, 2018
@lukebigum
(choria-io#193) dynamically look up path to Puppet, falling back to h…
4411efb 
…ard coded path
@lukebigum lukebigum mentioned this issue Aug 30, 2018
Merged
lukebigum added a commit to lukebigum/puppet-mcollective that referenced this issue Aug 31, 2018
@lukebigum
(choria-io#193) dynamically look up path to Puppet, falling back to h…
8da2cb7 
…ard coded path
ripienaar added a commit that referenced this issue Sep 1, 2018
@ripienaar
Merge pull request #194 from lukebigum/puppet_path
9466d25 
(#193) dynamically look up path to Puppet, falling back to hard coded path
@ripienaar
Copy link
Member

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ripienaar @lukebigum