feat: Use HEAD request to check if es_visibility index exists #585
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 was changed
curl
is now usingHEAD
request to ensure index existence and will result in 200/404 depending on the the result.I decided to propose
HEAD
instead ofGET
as I believe we don't need all of the outputGET /index
will produce. See Context below.Context
Both Elasticsearch and Opensearch support the following requests types to validate index existence:
GET /index
- ES docs | OS docsHEAD /index
- ES docs | OS docsWhy?
Please see #583
Checklist
Closes [Bug] Failed to validate ES index due to PUT request usage #583
How was this tested:
curl
embedded in theadmintools
support--head
arg properlyNo