You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my context, I am using the ep_pre_request_args hook to add the sslverify argument to false to the Opensearch service in my local environment. As the request is made from the wp_remote_get function, the hook call is not made in this case.
Designs
No response
Describe alternatives you've considered
I changed the line to run with ElasticPress\Elasticsearch::remote_request and it works in my context.
$ wp elasticpress stats
====== Stats for: localhostwp-post-1 ======
Documents: 871
Index Size: 609,44 KB
Index Size (including replicas): 609,44 KB
====== End Stats ======
I believe that this solution was designed this way because some part of ElasticPress\Elasticsearch::remote_request cannot be executed. that's right, the solution might be add this method's filter hooks to these requests.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Hi @edpittol, thank you very much for opening the issue (always good to see familiar faces around!)
Would you mind opening a PR changing those wp_remote_get calls to Elasticsearch::remote_request? Thanks!
It will be a pleasure to contribute a little more. I spent a time setting up the environment to run the tests. My expectation is to open the PR in a few days.
Is your enhancement related to a problem? Please describe.
The request to the
_recovery
endpoint in the CLIstatus
command and to_stats
instats
are not executed in theElasticPress\Elasticsearch::remote_request
method.In my context, I am using the
ep_pre_request_args
hook to add thesslverify
argument tofalse
to the Opensearch service in my local environment. As the request is made from thewp_remote_get
function, the hook call is not made in this case.Designs
No response
Describe alternatives you've considered
I changed the line to run with
ElasticPress\Elasticsearch::remote_request
and it works in my context.Status
Complete output
Stats
I believe that this solution was designed this way because some part of
ElasticPress\Elasticsearch::remote_request
cannot be executed. that's right, the solution might be add this method's filter hooks to these requests.Code of Conduct
The text was updated successfully, but these errors were encountered: