-
Notifications
You must be signed in to change notification settings - Fork 855
Allow not installing Elasticsearch deb repository key #526
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for fixing this up!
jenkins test this please |
Is the failure that CI is giving. Was this working for you when you tested it? Wondering if this could be a difference between ansible versions. In any case I think it is going to need to be checking for a non-empty string. Also the other GitHub status check is failing as you haven't signed the CLA |
If a variable is set in Ansible, there is no way to unset it ever again, i.e. 'null' or '~' do not work. Since this value is set in defaults we have to check for content instead of defined.
Ah, I only had tested with Validated it for the defaults now, too :).
Waiting for my supervisor's approval to sign the CLA, but I've seen that, thanks :). |
jenkins test this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
If a variable is set in Ansible, there is no way to unset it ever again, i.e. setting
es_apt_key: null
ores_apt_key: ~
do not work.Since this value is set in
defaults/main.yml
we have to perform a boolean check on the string.