From 4a36071be379e3d1d1d4822484e4818d326418ec Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Thu, 8 Feb 2024 16:59:56 -0500 Subject: [PATCH 1/3] Fixing email example --- website/docs/docs/dbt-cloud-apis/user-tokens.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-cloud-apis/user-tokens.md b/website/docs/docs/dbt-cloud-apis/user-tokens.md index 7fbcabfdd71..85c79a70e21 100644 --- a/website/docs/docs/dbt-cloud-apis/user-tokens.md +++ b/website/docs/docs/dbt-cloud-apis/user-tokens.md @@ -35,7 +35,7 @@ The migration to PATs is critical if you are using user API keys today. The curr * Personal access tokens are more secure. * To promote least privilege and high security assurance for your dbt Cloud accounts, we highly recommend moving to the new account-scoped personal access tokens. * You must create and use unique tokens in each one of your dbt Cloud accounts that share the same email address. - * For example, if paul@atreides.com belongs to two dbt Cloud accounts: Spice Harvesting Account and Guild Navigator Account. Prior to this release, the same API key was used to access both of these accounts. + * For example, if paul.atreides@example.com belongs to two dbt Cloud accounts: Spice Harvesting Account and Guild Navigator Account. Prior to this release, the same API key was used to access both of these accounts. * After this release, Paul has to individually go into these accounts and create a unique PAT for each account he wants to access the API for. These PATs are account-specific and not user specific. * Cross-Account API endpoints will change in behavior when using the personal access tokens. * These are namely /v2/accounts and /v3/accounts. Since all PATs are now account specific, getting all accounts associated to a username cannot work. /v3/accounts will only return account metadata that’s relevant to the PAT that’s being used. From 2e05d9aca9308efbf396a619e518acde8cc80f70 Mon Sep 17 00:00:00 2001 From: Tania <92768464+Tonayya@users.noreply.github.com> Date: Fri, 9 Feb 2024 22:29:29 +1100 Subject: [PATCH 2/3] Update source.md --- website/docs/reference/commands/source.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/website/docs/reference/commands/source.md b/website/docs/reference/commands/source.md index 697ae2b5fcc..f8a9e7088e3 100644 --- a/website/docs/reference/commands/source.md +++ b/website/docs/reference/commands/source.md @@ -6,9 +6,7 @@ id: "source" The `dbt source` command provides subcommands that are useful when working with source data. This command provides one subcommand, `dbt source freshness`. -:::info -If you're using an older version of dbt Core (before v0.21), the old name of the `freshness` subcommand was `snapshot-freshness`. (It has nothing to do with [snapshots](/docs/build/snapshots), which is why we renamed it.) Each time you see the command below, you'll need to specify it as `dbt source snapshot-freshness` instead of `dbt source freshness`. -::: + ### dbt source freshness From 76a1416954b9eaf928d75f8948a6eb737a3bc3ee Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 9 Feb 2024 11:50:19 +0000 Subject: [PATCH 3/3] Update user-tokens.md updating to the _main_ support email and other fixes. --- website/docs/docs/dbt-cloud-apis/user-tokens.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/website/docs/docs/dbt-cloud-apis/user-tokens.md b/website/docs/docs/dbt-cloud-apis/user-tokens.md index 85c79a70e21..ca8034439d5 100644 --- a/website/docs/docs/dbt-cloud-apis/user-tokens.md +++ b/website/docs/docs/dbt-cloud-apis/user-tokens.md @@ -33,18 +33,18 @@ The migration to PATs is critical if you are using user API keys today. The curr There are a few things to understand if you are using a user API key today: * Personal access tokens are more secure. - * To promote least privilege and high security assurance for your dbt Cloud accounts, we highly recommend moving to the new account-scoped personal access tokens. + * To promote the least privilege and high-security assurance for your dbt Cloud accounts, we highly recommend moving to the new account-scoped personal access tokens. * You must create and use unique tokens in each one of your dbt Cloud accounts that share the same email address. - * For example, if paul.atreides@example.com belongs to two dbt Cloud accounts: Spice Harvesting Account and Guild Navigator Account. Prior to this release, the same API key was used to access both of these accounts. + * For example, if paul.atreides@example.com belongs to two dbt Cloud accounts: Spice Harvesting Account and Guild Navigator Account. Before this release, the same API key was used to access both of these accounts. * After this release, Paul has to individually go into these accounts and create a unique PAT for each account he wants to access the API for. These PATs are account-specific and not user specific. * Cross-Account API endpoints will change in behavior when using the personal access tokens. - * These are namely /v2/accounts and /v3/accounts. Since all PATs are now account specific, getting all accounts associated to a username cannot work. /v3/accounts will only return account metadata that’s relevant to the PAT that’s being used. + * These are namely /v2/accounts and /v3/accounts. Since all PATs are now account specific, getting all accounts associated with a username cannot work. /v3/accounts will only return account metadata that’s relevant to the PAT that’s being used. * User account metadata will only contain information about the specific account under which the request is being made. * Any other accounts that belong to that user account will need to be requested through the PAT that belongs to that account. :::warning Undocumented APIs -If you’re using any undocumented and unsupported API endpoints, please note that these can be deprecated without any notice. If you are using any undocumented endpoints and have use-cases that are not satisfied by the current API, please reach out to [support@dbt.com](mailto:support@dbt.com). +If you’re using any undocumented and unsupported API endpoints, please note that these can be deprecated without any notice. If you are using any undocumented endpoints and have use-cases that are not satisfied by the current API, please reach out to [support@getdbt.com](mailto:support@getdbt.com). ::: @@ -55,14 +55,14 @@ Are you using a user API key today to access dbt Cloud APIs in any of your workf 1. Make a list of all the places where you’re making a call to the dbt Cloud API using the dbt Cloud user API key. 2. Create a new personal access token under **Account Settings → API Tokens → Personal Tokens.** 3. Create and copy the new PAT to replace the old user API key. -4. Ensure that you’re using a PAT only where its needed. For any flows that requires a service account, please use a service token. Read the section below for more information. +4. Ensure that you’re using a PAT only where it's needed. For any flows that requires a service account, please use a service token. Read the section below for more information. ## User API tokens Each dbt Cloud user with a [Developer license](/docs/cloud/manage-access/seats-and-users) is issued an API token. This token can be used to execute queries against the dbt Cloud API on the user's behalf. User API tokens inherit the -permissions of the user the that they were created for. +permissions of the user that they were created for. You can find your user API token in the **Profile page** under the **API Access** label. @@ -72,4 +72,4 @@ label. ## FAQs - \ No newline at end of file +