Merged
Conversation
…settings Adds a new elasticsearch_cluster_settings dictionary variable that applies persistent cluster settings via the PUT _cluster/settings API after the cluster is healthy. Reads current settings first and only sends the PUT when values differ. Runs once per play on the CA host. This provides a general mechanism for any cluster-level setting, replacing the need for one-off variables for individual settings. LogsDB, watermarks, recovery throttling, and any other cluster setting can now be expressed as a dict entry. Closes #21
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds
elasticsearch_cluster_settings, a dictionary variable that applies persistent cluster settings via thePUT _cluster/settingsAPI after the cluster is healthy. The task reads current settings first and only applies when values differ, so subsequent runs are idempotent and report no changes.This replaces the need for one-off variables for individual cluster settings. Any setting supported by the cluster settings API can be used — LogsDB, watermarks, recovery throttling, allocation awareness, etc.
The
elasticsearch_defaultscenario tests this withaction.destructive_requires_nameand verifies it via the cluster settings API in the verify playbook.Closes #21