hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-09-11 10:46:25 +03:00
Code Issues Projects Releases Wiki Activity

Fix URL paths in Data Connector Datasets readme

Browse Source 
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7841
GitOrigin-RevId: 02d8a838d8ff7e18af100ca7191459428ddd016b
This commit is contained in:
Daniel Chambers 2023-02-07 14:51:32 +11:00 committed by hasura-bot
parent 2d513ace63
commit a5578cb4bd
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
dc-agents/README.md
View File

@ -2199,9 +2199,9 @@ Datasets are represented by abstract names referencing database-schema templates
The `/datasets/:name` resource has the following methods:
* `GET /datasets/:template_name` -> `{"exists": true|false}`
* `POST /datasets/:clone_name {"from": template_name}` -> `{"config": {...}}`
* `DELETE /datasets/:clone_name` -> `{"message": "success"}`
* `GET /datasets/templates/:template_name` -> `{"exists": true|false}`
* `POST /datasets/clones/:clone_name {"from": template_name}` -> `{"config": {...}}`
* `DELETE /datasets/clones/:clone_name` -> `{"message": "success"}`
The `POST` method is the most significant way to interact with the API. It allows for cloning a dataset template to a new name. The new name can be used to delete the dataset, and the config returned from the POST API call can be used as the config header for non-dataset interactions such as queries.