From 285d908cb5d134b5b342c3870a1c2dc432937ecb Mon Sep 17 00:00:00 2001 From: Evgeny Oshchepkov Date: Wed, 17 Jul 2024 22:40:26 +0200 Subject: [PATCH 1/2] Update embeddable.md --- third-party-tools/embeddable.md | 29 ++++++++++++----------------- 1 file changed, 12 insertions(+), 17 deletions(-) diff --git a/third-party-tools/embeddable.md b/third-party-tools/embeddable.md index 1903dccf1..d0e5c0f22 100644 --- a/third-party-tools/embeddable.md +++ b/third-party-tools/embeddable.md @@ -65,23 +65,18 @@ The above represents a `CREATE` action, but all `CRUD` operations are available. The `apiKey` can be found by clicking “**Publish**” on one of your Embeddable dashboards. -The `name` is a unique name to identify this **connection**. - -- By default your **data models** will look for a **connection** called - “default”, but you can supply models with different - [**data_source**](https://cube.dev/docs/reference/data-model/cube#data_source) - names to support connecting different **data models** to different - **connections**. To do so , specify the - **[data_source](https://cube.dev/docs/reference/data-model/cube#data_source)** - name in the model. - -The `type` tells Embeddable which driver to use, in this case `questdb`. You can -also connect multiple datasources like `postgres`, `bigquery` or `mongodb`. For -a full list, see -[the documentaiton](https://cube.dev/docs/product/configuration/data-sources). - -The `credentials` is a javascript object containing the credentials expected by -the driver: +The `name` is a unique name to identify this connection. +- By default your data models will look for a connection called “default”, but you can supply your models with different `data_source` names to support connecting different data models to different connections (simply specify the data_source name in the model) + +The `type` tells Embeddable which driver to use + +- Here you'll want to use `questbd`, but you can connect multiple different datasources to one Embeddable workspace so you may use others such as: `postgres`, `bigquery`, `mongodb`, etc. + +The `credentials` is a javascript object containing the necessary credentials expected by the driver +- These are securely encrypted and only used to retrieve exactly the data you have described in your data models. +Embeddable strongly encourage you to create a read-only database user for each connection (Embeddable will only ever read from your database, not write). + +In order to support connecting to different databases for prod, qa, test, etc (or to support different databases for different customers) you can assign each connection to an environment (see [Environments API](https://www.notion.so/Environments-API-497169036b5148b38f7936aa75e62949?pvs=21)). - Credentials are securely encrypted and only used to retrieve exactly the data described in the data models. From ee53e8644d78f5b0494722857268ea328e009ae1 Mon Sep 17 00:00:00 2001 From: Evgeny Oshchepkov Date: Wed, 17 Jul 2024 22:43:07 +0200 Subject: [PATCH 2/2] Update embeddable.md --- third-party-tools/embeddable.md | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/third-party-tools/embeddable.md b/third-party-tools/embeddable.md index d0e5c0f22..a058a762e 100644 --- a/third-party-tools/embeddable.md +++ b/third-party-tools/embeddable.md @@ -66,6 +66,7 @@ The `apiKey` can be found by clicking “**Publish**” on one of your Embeddabl dashboards. The `name` is a unique name to identify this connection. + - By default your data models will look for a connection called “default”, but you can supply your models with different `data_source` names to support connecting different data models to different connections (simply specify the data_source name in the model) The `type` tells Embeddable which driver to use @@ -74,16 +75,6 @@ The `type` tells Embeddable which driver to use The `credentials` is a javascript object containing the necessary credentials expected by the driver - These are securely encrypted and only used to retrieve exactly the data you have described in your data models. -Embeddable strongly encourage you to create a read-only database user for each connection (Embeddable will only ever read from your database, not write). +- Embeddable strongly encourage you to create a read-only database user for each connection (Embeddable will only ever read from your database, not write). In order to support connecting to different databases for prod, qa, test, etc (or to support different databases for different customers) you can assign each connection to an environment (see [Environments API](https://www.notion.so/Environments-API-497169036b5148b38f7936aa75e62949?pvs=21)). - -- Credentials are securely encrypted and only used to retrieve exactly the data - described in the data models. -- Emeddable strongly encourages you to create a **read-only** database user for - each connection. Embeddable will only ever read from your database, not write. - -To support connecting to different databases for prod, qa, test, etc, or to -support different databases for different customers, you can assign each -**connection** to an **environment**. For more information, see -[Environments API](https://www.notion.so/Environments-API-497169036b5148b38f7936aa75e62949?pvs=21).