yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-09-02 05:33:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Added dbt cloud permissions (#16901)

Browse Source
This commit is contained in:
Onkar Ravgan 2024-07-04 06:39:09 +05:30 committed by GitHub
parent 6456512fbd
commit a8dd5e99e9
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
7 changed files with 24 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
openmetadata-docs/content/v1.3.x/connectors/ingestion/workflows/dbt/ingest-dbt-ui.md
View File

@ -128,7 +128,9 @@ File server path of the `manifest.json`, `catalog.json` and `run_results.json` f
Click on the the link [here](https://docs.getdbt.com/guides/getting-started) for getting started with dbt cloud account setup if not done already.
OpenMetadata uses dbt cloud APIs to fetch the `run artifacts` (manifest.json, catalog.json and run_results.json) from the most recent dbt run.
The APIs need to be authenticated using an Authentication Token. Follow the link [here](https://docs.getdbt.com/dbt-cloud/api-v2#section/Authentication) to generate an authentication token for your dbt cloud account.
The APIs need to be authenticated using an Authentication Token. Follow the link [here](https://docs.getdbt.com/docs/dbt-cloud-apis/service-tokens) to generate an authentication token for your dbt cloud account.
The `Account Viewer` role is the minimum requirement for the dbt cloud token.
{% image
src="/images/v1.3/features/ingestion/workflows/dbt/dbt-cloud.webp"

4
openmetadata-docs/content/v1.3.x/connectors/ingestion/workflows/dbt/ingest-dbt-yaml.md
View File

@ -493,6 +493,8 @@ source:
### 6. dbt Cloud
In this configuration we will be fetching the dbt `manifest.json`, `catalog.json` and `run_results.json` files from dbt cloud APIs.
The `Account Viewer` permission is the minimum requirement for the dbt cloud token.
{% codePreview %}
{% codeInfoContainer %}
@ -514,7 +516,7 @@ For example, if the URL is `https://cloud.getdbt.com/#/accounts/1234/projects/67
{% /codeInfo %}
{% codeInfo srNumber=63 %}
- **dbtCloudJobId**: InIn case of multiple jobs in a dbt cloud account, specify the job's ID from which you want to extract the dbt run artifacts.
- **dbtCloudJobId**: In case of multiple jobs in a dbt cloud account, specify the job's ID from which you want to extract the dbt run artifacts.
If left empty, the dbt artifacts will be fetched from the most recent run on dbt cloud.
The value entered should be a `numeric` value.
{% /codeInfo %}

4
openmetadata-docs/content/v1.4.x/connectors/ingestion/workflows/dbt/ingest-dbt-ui.md
View File

@ -128,7 +128,9 @@ File server path of the `manifest.json`, `catalog.json` and `run_results.json` f
Click on the the link [here](https://docs.getdbt.com/guides/getting-started) for getting started with dbt cloud account setup if not done already.
OpenMetadata uses dbt cloud APIs to fetch the `run artifacts` (manifest.json, catalog.json and run_results.json) from the most recent dbt run.
The APIs need to be authenticated using an Authentication Token. Follow the link [here](https://docs.getdbt.com/dbt-cloud/api-v2#section/Authentication) to generate an authentication token for your dbt cloud account.
The APIs need to be authenticated using an Authentication Token. Follow the link [here](https://docs.getdbt.com/docs/dbt-cloud-apis/service-tokens) to generate an authentication token for your dbt cloud account.
The `Account Viewer` permission is the minimum requirement for the dbt cloud token.
{% image
src="/images/v1.4/features/ingestion/workflows/dbt/dbt-cloud.webp"

4
openmetadata-docs/content/v1.4.x/connectors/ingestion/workflows/dbt/ingest-dbt-yaml.md
View File

@ -493,6 +493,8 @@ source:
### 6. dbt Cloud
In this configuration we will be fetching the dbt `manifest.json`, `catalog.json` and `run_results.json` files from dbt cloud APIs.
The `Account Viewer` permission is the minimum requirement for the dbt cloud token.
{% codePreview %}
{% codeInfoContainer %}
@ -514,7 +516,7 @@ For example, if the URL is `https://cloud.getdbt.com/#/accounts/1234/projects/67
{% /codeInfo %}
{% codeInfo srNumber=63 %}
- **dbtCloudJobId**: InIn case of multiple jobs in a dbt cloud account, specify the job's ID from which you want to extract the dbt run artifacts.
- **dbtCloudJobId**: In case of multiple jobs in a dbt cloud account, specify the job's ID from which you want to extract the dbt run artifacts.
If left empty, the dbt artifacts will be fetched from the most recent run on dbt cloud.
The value entered should be a `numeric` value.
{% /codeInfo %}

4
openmetadata-docs/content/v1.5.x-SNAPSHOT/connectors/ingestion/workflows/dbt/ingest-dbt-ui.md
View File

@ -128,7 +128,9 @@ File server path of the `manifest.json`, `catalog.json` and `run_results.json` f
Click on the the link [here](https://docs.getdbt.com/guides/getting-started) for getting started with dbt cloud account setup if not done already.
OpenMetadata uses dbt cloud APIs to fetch the `run artifacts` (manifest.json, catalog.json and run_results.json) from the most recent dbt run.
The APIs need to be authenticated using an Authentication Token. Follow the link [here](https://docs.getdbt.com/dbt-cloud/api-v2#section/Authentication) to generate an authentication token for your dbt cloud account.
The APIs need to be authenticated using an Authentication Token. Follow the link [here](https://docs.getdbt.com/docs/dbt-cloud-apis/service-tokens) to generate an authentication token for your dbt cloud account.
The `Account Viewer` permission is the minimum requirement for the dbt cloud token.
{% image
src="/images/v1.5/features/ingestion/workflows/dbt/dbt-cloud.webp"

4
openmetadata-docs/content/v1.5.x-SNAPSHOT/connectors/ingestion/workflows/dbt/ingest-dbt-yaml.md
View File

@ -493,6 +493,8 @@ source:
### 6. dbt Cloud
In this configuration we will be fetching the dbt `manifest.json`, `catalog.json` and `run_results.json` files from dbt cloud APIs.
The `Account Viewer` permission is the minimum requirement for the dbt cloud token.
{% codePreview %}
{% codeInfoContainer %}
@ -514,7 +516,7 @@ For example, if the URL is `https://cloud.getdbt.com/#/accounts/1234/projects/67
{% /codeInfo %}
{% codeInfo srNumber=63 %}
- **dbtCloudJobId**: InIn case of multiple jobs in a dbt cloud account, specify the job's ID from which you want to extract the dbt run artifacts.
- **dbtCloudJobId**: In case of multiple jobs in a dbt cloud account, specify the job's ID from which you want to extract the dbt run artifacts.
If left empty, the dbt artifacts will be fetched from the most recent run on dbt cloud.
The value entered should be a `numeric` value.
{% /codeInfo %}

6
openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/workflows/dbt.md
View File

@ -79,6 +79,8 @@ $$section
### dbt Cloud Config $(id="dbtCloudConfig")
In this configuration we will be fetching the dbt `manifest.json`, `catalog.json` and `run_results.json` files from dbt cloud APIs.
The `Account Viewer` permission is the minimum requirement for the dbt cloud token.
$$
$$section
@ -101,6 +103,8 @@ $$section
In case of multiple projects in a dbt cloud account, specify the project's ID from which you want to extract the dbt run artifacts.
If left empty, the dbt artifacts will be fetched from the most recent run on dbt cloud.
The value entered should be a `numeric` value.
$$
$$section
@ -109,6 +113,8 @@ $$section
In case of multiple jobs in a dbt cloud account, specify the job's ID from which you want to extract the dbt run artifacts.
If left empty, the dbt artifacts will be fetched from the most recent run on dbt cloud.
The value entered should be a `numeric` value.
$$
$$section