Vacha Shah
Vacha Shah
Coming from https://github.com/opensearch-project/opensearch-clients/issues/59, run tests on a cron basis to catch failures early.
Coming from https://github.com/opensearch-project/opensearch-clients/issues/59, run tests on a cron basis to catch failures early.
### Is your feature request related to a problem? Related to https://github.com/opensearch-project/opensearch-clients/issues/19 ### What solution would you like? Re-use the generator that generates API Code that maintains backwards compatibility with...
### Is your feature request related to a problem? We test our clients for Linux platform but we do not know if these clients work smoothly on platforms like windows/mac...
Coming from https://github.com/opensearch-project/opensearch-clients/issues/59, run tests on a cron basis to catch failures early.
### Is your feature request related to a problem? We test our clients for Linux platform but we do not know if these clients work smoothly on platforms like windows/mac...
Coming from https://github.com/opensearch-project/opensearch-py/pull/511#pullrequestreview-1655403319, as @dblock suggested, we should have tests for all the generated code we are putting in, starting with some basic tests that are also generated.
Coming from https://github.com/opensearch-project/opensearch-clients/issues/59, run tests on a cron basis to catch failures early.
### What is the bug? [Compatibility matrix](https://github.com/opensearch-project/opensearch-ruby/blob/main/COMPATIBILITY.md) for the client gems is outdated. Update the matrix for the released gems. ### How can one reproduce the bug? See https://github.com/opensearch-project/opensearch-ruby/blob/main/COMPATIBILITY.md. ###...
Coming from https://github.com/opensearch-project/opensearch-clients/issues/59, run tests on a cron basis to catch failures early.