third_codes/eland
1
0
Fork 0
mirror of https://github.com/elastic/eland.git synced 2025-07-11 00:02:14 +08:00
Code Issues Packages Projects Releases Wiki Activity

Support HTTP proxies in eland_import_hub_model (#688)

Browse Source 
* Document TLS/SSL options for import script

* Mention --help option

* Add HTTP proxy support

* Mention HTTP_PROXY too

---------

Co-authored-by: David Kyle <david.kyle@elastic.co>
This commit is contained in:
Quentin Pradet 2024-05-02 21:03:44 +04:00 committed by GitHub
parent f7f6e0aba9
commit fd38e26df1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/guide/machine-learning.asciidoc
View File

@ -154,6 +154,23 @@ underscores `__`.
--
[discrete]
[[ml-nlp-pytorch-proxy]]
==== Connect to Elasticsearch through a proxy
Behind the scenes, Eland uses the `requests` Python library, which
https://requests.readthedocs.io/en/latest/user/advanced/#proxies[allows configuring
proxies through an environment variable]. For example, to use an HTTP proxy to connect to
an HTTPS Elasticsearch cluster, you need to set the `HTTPS_PROXY` environment variable
when invoking Eland:
[source,bash]
--------------------------------------------------
HTTPS_PROXY=http://proxy-host:proxy-port eland_import_hub_model ...
--------------------------------------------------
If you disabled security on your Elasticsearch cluster, you should use `HTTP_PROXY`
instead.
[discrete]
[[ml-nlp-pytorch-auth]]

1
eland/cli/eland_import_hub_model.py
View File

@ -164,6 +164,7 @@ def get_es_client(cli_args, logger):
"request_timeout": 300,
"verify_certs": cli_args.insecure,
"ca_certs": cli_args.ca_certs,
"node_class": "requests",
}
# Deployment location