added encoded API key placeholder for updated api_key elasticsearch authentication.

[SamoraHunter]

No description provided.

[preciserobot]

The documentation on the elasticsearch python library is quite non-specific but it appears the api_key username:password tuple is the (api_key.id, api_key.api_key), as described here.

We generally issue key ID and the key secret (plain and base64 encoded), so we should be able to use the existing implementation with some added documentation.

CORRECTION: We do not currently issue the key ID but the key name. I can change this internally to make it compatible with the current version of this repo.

[SamoraHunter]

The documentation on the elasticsearch python library is quite non-specific but it appears the api_key username:password tuple is the (api_key.id, api_key.api_key), as described here.

We generally issue key ID and the key secret (plain and base64 encoded), so we should be able to use the existing implementation with some added documentation.

CORRECTION: We do not currently issue the key ID but the key name. I can change this internally to make it compatible with the current version of this repo.

That link is for version 7.17,

I think the version we're running is https://www.elastic.co/guide/en/elasticsearch/client/python-api/8.17/connecting.html

api_key="api_key",

The jupyterhub docker image also users 8.17:
https://github.com/CogStack/cogstack-jupyter-hub/blob/master/requirements.txt

[preciserobot]

The documentation on the elasticsearch python library is quite non-specific but it appears the api_key username:password tuple is the (api_key.id, api_key.api_key), as described here.
We generally issue key ID and the key secret (plain and base64 encoded), so we should be able to use the existing implementation with some added documentation.
CORRECTION: We do not currently issue the key ID but the key name. I can change this internally to make it compatible with the current version of this repo.

That link is for version 7.17,

I think the version we're running is https://www.elastic.co/guide/en/elasticsearch/client/python-api/8.17/connecting.html

api_key="api_key",

The jupyterhub docker image also users 8.17: https://github.com/CogStack/cogstack-jupyter-hub/blob/master/requirements.txt

The docs for 8.17 still show the string|tuple|None signature. Looks like this is retained here.

Indeed the implementation for elasticsearch-py 8.17 confirms this here:
client/__init__py:143,430
_base.py:128
utils.py:254