Use discovery.seed_providers instead of discovery.zen.hosts_provider starting 7.x #2029
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.
Starting Elasticsearch 7.0,
discovery.zen.hosts_provider
is deprecatedin favor of
discovery.seed_providers
.The setting is removed in 8.0, preventing any 8.0 cluster to bootstrap.
This commit switches over the Elasticsearch version when building the
elasticsearch.yml configuration, to make sure versions lower than 7.0
use
discovery.zen.hosts_provider
, and other versions use the newerdiscovery.seed_providers
.I did some manual testing, also covered by E2E tests: