Daniel Widdis
Daniel Widdis
**What is the bug?** I'm trying to improve code coverage on #2430. The build is passing all the unit and integ tests, but is failing on lack of coverage: ```...
### Is your feature request related to a problem? This is a more specific plan to implement https://github.com/opensearch-project/flow-framework/issues/795 Flow Framework templates are essentially a configuration-as-code implementation, conceptually not much different...
### What is the bug? The `WorkflowRequest` class doesn't serialize the use case and default parameters over transport. The `writeTo()` only writes the provision parameter and params map: https://github.com/opensearch-project/flow-framework/blob/cf1016fd72e0f9196db498cbb52f4a57bafadade/src/main/java/org/opensearch/flowframework/transport/WorkflowRequest.java#L197-L206 Similarly,...
## What/Why ### What are you proposing? The [OpenSearch API Specification](https://github.com/opensearch-project/opensearch-api-specification) repo includes a [Test Suite](https://github.com/opensearch-project/opensearch-api-specification/blob/main/TESTING_GUIDE.md) that allows for easy YAML-based test writing. We should use that functionality to test...
### Is your feature request related to a problem? Currently the Workflow State resource document is only additive, using a Painless script during provisioning to append to a list. This...
### Is your feature request related to a problem? Because WorkflowState updates have only been additive, the Deprovisioning workflow only updates once at the end of deprovisioning with a "remaining...
### Is your feature request related to a problem? Unit testing is unable to handle end-to-end "how does an extension respond to a REST request from OpenSearch". When writing "hello...
### What is the bug? Coming from https://github.com/opensearch-project/OpenSearch/issues/14800#issuecomment-2237118907 I need to add specs/test for two new search response processors. However, non of the existing processors exist to serve as an...
**Describe the bug** Coming from https://github.com/opensearch-project/OpenSearch/issues/7066#issuecomment-1501541654 Internally to OpenSearch, the cluster state is retrieved by handling the `ClusterStateAction` / `TransportClusterStateAction` / `ClusterStateRequest` / `ClusterStateResponse` implementations. The [`RestClusterStateAction`](https://github.com/opensearch-project/OpenSearch/blob/e3339e8de65b580fa767e2d344d6a3a50116e84b/server/src/main/java/org/opensearch/rest/action/admin/cluster/RestClusterStateAction.java#L95-L97) exposes the API...
### What is the bug? The enum defined for the client uses lower case values for the `ZeroTermsQuery` enum: https://github.com/opensearch-project/opensearch-java/blob/08e7e6504d4e6029640940f4bb4670e5e183c700/java-client/src/main/java/org/opensearch/client/opensearch/_types/query_dsl/ZeroTermsQuery.java#L38-L42 However, this enum is [defined on OpenSearch with traditional all-caps...