-
Notifications
You must be signed in to change notification settings - Fork 289
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
the sensu-plugin gem is incorrectly installed with the system ruby instead of the embedded ruby #688
Comments
@ghoneycutt Is the scope of this the default behavior of the module to be released to end users, or restricted to the vagrant environment, e.g. |
jeffmccune
added a commit
to jeffmccune/sensu-puppet
that referenced
this issue
Jun 28, 2017
Without this patch the behavior of sensu-plugin is managed by the default package provider for the system, e.g. gem. This patch changes the default behavior to use the embedded ruby version at `/opt/sensu/embedded/bin/gem` via the built in provider.
PR-694 is ready for review. |
Not just vagrant, you're on the right track here by only using the embedded ruby. |
ghoneycutt
added a commit
that referenced
this issue
Jun 28, 2017
…lugin (GH-688) Default sensu-plugin gem to use sensu_gem provider
jeffmccune
added a commit
to jeffmccune/sensu-puppet
that referenced
this issue
Jun 29, 2017
Without this patch the default behavior is to manage sensu-plugin using the system `gem` command via the gem provider. This is a problem because this version combination is unknown and untested. The embedded ruby should be used for supportability and predictable behavior. This patch changes the default behavior to use the embedded ruby version at `/opt/sensu/embedded/bin/gem` via the `sensu_gem` provider shipped in this module. closes sensu#688
Released in v2.7.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should install the plugin and anything else using the embedded ruby and not the system ruby.
The text was updated successfully, but these errors were encountered: