Skip to content

Commit fbaad7d

Browse files
committed
Remove the legacy client generator
1 parent e6e8087 commit fbaad7d

27 files changed

+4
-705
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -32,23 +32,10 @@ you don't have Elasticsearch running locally the integration tests will be skipp
3232
All the API methods (any method in `elasticsearch.client` classes decorated
3333
with `@query_params`) are actually auto-generated from the
3434
[rest-api-spec](https://github.com/elastic/elasticsearch/tree/master/rest-api-spec/src/main/resources/rest-api-spec/api)
35-
found in the `Elasticsearch` repository. Any changes to those methods should be
36-
done either by submitting a PR to Elasticsearch itself (in case of adding or
37-
modifying any of the API methods) or to the [Generate
38-
Script](https://github.com/elastic/elasticsearch-py/blob/master/utils/generate_api.py).
39-
40-
To run the code generation make sure you have pre-requisites installed:
41-
42-
* by running `python -m pip install -e '.[develop]'`
43-
* having the [elasticsearch](https://github.com/elastic/elasticsearch) repo
44-
cloned on the same level as `elasticsearch-py` and switched to appropriate
45-
version
46-
47-
Then you should be able to run the code generation by invoking:
48-
49-
```
50-
$ python utils/generate-api.py 8.0.0-SNAPSHOT
51-
```
35+
found in the `Elasticsearch` or the [Elasticsearch specification](https://github.com/elastic/elasticsearch-specification)
36+
repositories. Any changes to those methods should be done either by submitting a PR to one of these repositories
37+
instead of directly to the Python client otherwise your change will be overwritten the
38+
next time the APIs are generated.
5239

5340
## Contributing Code Changes
5441

0 commit comments

Comments
 (0)