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.
elasticsearch: fix keystore restart notify and non-rolling upgrade #541
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
Uh oh!
There was an error while loading. Please reload this page.
elasticsearch: fix keystore restart notify and non-rolling upgrade #541
Changes from all commits
690a83951f5842c90ac167f573d8File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check warning on line 76 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 76 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 76 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 94 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 94 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 94 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 174 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 174 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 174 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 192 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 192 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 192 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 208 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 208 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 208 in roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
var-naming[no-role-prefix]
Check warning on line 277 in roles/elasticsearch/tasks/main.yml
[MEDIUM] Communication Over HTTP
Uh oh!
There was an error while loading. Please reload this page.