From a5578cb4bd1b8913079a40c2a117f616e5568259 Mon Sep 17 00:00:00 2001 From: Daniel Chambers Date: Tue, 7 Feb 2023 14:51:32 +1100 Subject: [PATCH] Fix URL paths in Data Connector Datasets readme PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7841 GitOrigin-RevId: 02d8a838d8ff7e18af100ca7191459428ddd016b --- dc-agents/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/dc-agents/README.md b/dc-agents/README.md index 556893912ca..00e3c733f52 100644 --- a/dc-agents/README.md +++ b/dc-agents/README.md @@ -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.