-
Notifications
You must be signed in to change notification settings - Fork 22
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
use puppetserver_gem when installing on JVM puppetserver #2
Comments
This was one thing I was trying to address with #8. I finally got some time to redeploy that code from scratch on a JVM puppetserver. I believe that there is more that needs to be addressed than just the gem provider. The gem is needed with puppetserver_gem for the generate token function to work. However, when installing the with puppetserver_gem, the validator scripts were placed in /opt/puppetlabs/server/data/puppetserver/jruby-gems/bin/autosign-validator. If this was set as the validator script for autosign in puppet.conf it would fail to run the script to validate a node. My bandaid solution was to install the gem with both puppet_gem and puppetserver_gem. When compiling, the token is generated with the puppetserver_gem package and the validator script located /opt/puppetlabs/puppet/bin/autosign-validator uses the puppet_gem package. This seems to work but I don't love having to install the gem twice. There may not be a way around it but I thought I'd throw it out there if anyone has any feedback. |
I think the approach we ought to take here is to write puppet code that installs the gem via both providers, but I'm not sure how to do that; I think there'd be a resource conflict. We could use an exec as a hack, but that feels pretty gross. Maybe less gross than having to do it manually, though. |
When trying to install via puppetserver_gem I get
|
Fixes #2 - use puppetserver_gem when installing on JVM puppetserver
as-is, the autosign module is not usable on JVM puppetserver without additional code because puppetserver gems must be installed using puppetserver_gem, not the normal gem package provider.
The text was updated successfully, but these errors were encountered: