Changed API Key from tuple to encoding in the docs

[iuliaferoli]

still to be added - the mention in the readthedocs index
no longer applicable with the redirect from master to latest

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[pquentin]

Great, thanks!

[pquentin]

This looks good and I don't want to delay this pull request further, but for future work I think we should encourage users going to Kibana instead which has a clear UI and docs (https://www.elastic.co/guide/en/kibana/current/api-keys.html) and displays the correct encoding by default:

[pquentin]

Here's the result: https://elasticsearch-py_bk_2477.docs-preview.app.elstc.co/guide/en/elasticsearch/client/python-api/master/connecting.html#auth-apikey.

I don't understand the sentence:

You can configure the client to use Elasticsearch’s API Key for connecting to your cluster. Note that you need the API Key encoding you can generated in Kibana.

We also need to keep the Elasticsearch link for users that don't have Kibana. This all could have been done in a future pull request

[iuliaferoli]

Changed to include both methods

[iuliaferoli]

Also added the same change in the init so it shows up on https://elasticsearch-py.readthedocs.io/en/latest/api/elasticsearch.html

[pquentin]

Thanks! LGTM.