* Re-enable integration tests for 1.x versions of OpenSearch
Signed-off-by: Vacha Shah <vachshah@amazon.com>
* Fixing integ tests after re-enabling 1.x versions
Signed-off-by: Vacha Shah <vachshah@amazon.com>
* Separating out versions
Signed-off-by: Vacha Shah <vachshah@amazon.com>
* Breaking changes for type removal
Signed-off-by: Vacha Shah <vachshah@amazon.com>
* Adding support to test against unreleased OpenSearch
Signed-off-by: Vacha Shah <vachshah@amazon.com>
* Formatting
Signed-off-by: Vacha Shah <vachshah@amazon.com>
* Addressing comments to refactor run-opensearch.sh
Signed-off-by: Vacha Shah <vachshah@amazon.com>
Some OpenSearch REST APIs will return a Content-Type of text/plain for certain
status codes which will trigger logging when the response is not parsable as
JSON. Checking the content-type first avoids this error.
This frequently happens with 401s, which occurs when we rotate user keys.
The input that triggers this behaviour can be triggered with `curl`:
```
$ curl -k -u"admin:wrong" -w"\n%{http_code}\n%{content_type}\n" https://localhost:9200/_cluster/health
Unauthorized
401
text/plain; charset=UTF-8
```
Signed-off-by: Trevor McCulloch <trevor.mcculloch@benchling.com>
The integration tests performs a deep checkout of
the opensearch repository. Instead, we can perform
a shallow clone the main branch to improve the speed
and performance of the tests.
Signed-off-by: Venu Vardhan Reddy Tekula <venu@chaoss.community>
Arnav Das