-
-
Notifications
You must be signed in to change notification settings - Fork 478
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
elasticsearch_keystore resource fails due to legacy instance code #1153
Comments
this actually made secrets management unusable with new module |
I've created a hackish, drop-in replacement for elasticsearch_keystore provider: https://github.com/psychonaut/puppet-elasticsearch/blob/keystore/lib/puppet/provider/elasticsearch_keystore/ruby.rb - it works but to be honest, I don't like this approach: since in new module there's only one keystore there's no point of creating resource for keystore. Moreover, even in the old instance version, it didn't check the value of the secret, it only checked if a secret with this name exists. The new approach should be built around secrets, not keystores. So instead of
it should be
|
Here is another "dirty" solution similar to the one provided by @psychonaut but also solves #983 |
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
Could not evaluate: Execution of '/usr/share/elasticsearch/bin/elasticsearch-keystore create' returned 1:
What behaviour did you expect instead
Successful execution of elasticsearch_keystore resource
Output log
Any additional information you'd like to impart
The resource fails because of legacy instance configuration in this definition,
puppet-elasticsearch/lib/puppet/provider/elasticsearch_keystore/ruby.rb
Line 30 in 7ef7983
The text was updated successfully, but these errors were encountered: