Fix example playbook #135
Merged
Fix example playbook #135
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The example playbook we provided would have installed Elastic Stack on all hosts. When writing it a change about choosing hosts to install slipped my mind. fixes #130
widhalmt
added
bug
afeefghannam89
approved these changes
Mar 30, 2023
ivareri
pushed a commit
to ivareri/ansible-collection-elasticstack
that referenced
this pull request
Jun 17, 2025
* Fix broken keys on some systems fixes NETWAYS#135 It looks like there are still some hosts where pkcs8 keys for Logstash Beats input must not be encrypted. The strange thing about it is that it works on some systems (CentOS 7) and on some it doesn't (so far Ubuntu 20.04). I tried recreating the keys and some other ways but the Ubuntu host didn't like encrypted keys at all. So here's a workaround. Several other potential issues came up and were fixed, namely: * There's now a variable to disable encryption of the key used for the Beats input in Logstash * Logstash certificates created with `certutil` get now a suffix to their name. This helps when you have different passwords for keys in different tools. Otherwise they overwrite each other and you don't know which file has which passphrase * Rename certificate archive
ivareri
pushed a commit
to ivareri/ansible-collection-elasticstack
that referenced
this pull request
Jun 17, 2025
The example playbook we provided would have installed Elastic Stack on all hosts. When writing it a change about choosing hosts to install slipped my mind. fixes NETWAYS#130
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The example playbook we provided would have installed Elastic Stack on all hosts. When writing it a change about choosing hosts to install slipped my mind.
fixes #130