Elasticsearch: Deprecate the usage of the database field in provisioning #66828
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.
What is this feature?
updates the documentation for elasticsearch datasource provisioning.
updates the provisioning files for the elastic gdev datasources
Which issue(s) does this PR fix?:
Related #59098
Special notes for your reviewer:
elastic datasources after after new provisioning
Deprecation notice
The
database
field has been deprecated in the Elasticsearch datasource provisioning files, please use theindex
field injsonData
instead.