From 3b6ac92a0cc6594ed45abd1a87d9a345f509227d Mon Sep 17 00:00:00 2001 From: Ly Nguyen Date: Thu, 22 Dec 2022 17:37:28 -0800 Subject: [PATCH 1/4] dbt Cloud RN: Private packages must be cloned --- .../private-packages-clone-git-token.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md diff --git a/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md b/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md new file mode 100644 index 00000000000..493ecc2862c --- /dev/null +++ b/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md @@ -0,0 +1,19 @@ +--- +title: "Private packages must be cloned using tokens provided by environment variables" +description: "Private packages must be cloned using tokens provided by environment variables." +sidebar_label: "Deprecation: Private packages must be cloned using tokens provided by environment variables" +tags: [Dec-23-2022] +--- + +The supported way for cloning private packages is using the [git clone method](/docs/build/packages#git-token-method), in which an appropriate token is passed into the package repository URL via an environment variable. + +There is a small user base that has been able to clone private GitHub packages using our native GitHub application without explicitly providing an access token. We are deprecating this functionality, as it’s limited in flexibility. + +If you have been using a package hosted in a private repository on GitHub, you must explicitly pass as access token into the URL going forward. See below for sample usage. + +```yaml + +packages: +- git: "https://{{env_var('DBT_ENV_SECRET_GIT_CREDENTIAL')}}@github.com/dbt-labs/awesome_repo.git" + +``` \ No newline at end of file From 74e27b91d6298117273d5dec8bdd5a11d6069645 Mon Sep 17 00:00:00 2001 From: Ly Nguyen Date: Fri, 23 Dec 2022 11:29:46 -0800 Subject: [PATCH 2/4] Content updates --- .../private-packages-clone-git-token.md | 20 ++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md b/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md index 493ecc2862c..9ccd137c03b 100644 --- a/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md +++ b/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md @@ -1,19 +1,25 @@ --- -title: "Private packages must be cloned using tokens provided by environment variables" -description: "Private packages must be cloned using tokens provided by environment variables." -sidebar_label: "Deprecation: Private packages must be cloned using tokens provided by environment variables" +title: "Private packages must be cloned using access tokens provided by environment variables" +description: "Private GitHub packages must be cloned using access tokens provided by environment variables." +sidebar_label: "Deprecation: Private packages must be cloned using access tokens" tags: [Dec-23-2022] --- -The supported way for cloning private packages is using the [git clone method](/docs/build/packages#git-token-method), in which an appropriate token is passed into the package repository URL via an environment variable. +The supported way for cloning private GitHub packages is to use the [git token method](/docs/build/packages#git-token-method), where an appropriate access token is passed into the package repository URL with an environment variable. -There is a small user base that has been able to clone private GitHub packages using our native GitHub application without explicitly providing an access token. We are deprecating this functionality, as it’s limited in flexibility. +There is a small number of people that has been able to clone private packages using dbt's native GitHub application without explicitly providing an access token. This functionality is being deprecated as it’s limited in flexibility. -If you have been using a package hosted in a private repository on GitHub, you must explicitly pass as access token into the URL going forward. See below for sample usage. +If you have been using a package hosted in a private repository on GitHub, you must start passing an access token into the URL. + +An example of passing an access token: + + ```yaml packages: - git: "https://{{env_var('DBT_ENV_SECRET_GIT_CREDENTIAL')}}@github.com/dbt-labs/awesome_repo.git" -``` \ No newline at end of file +``` + + \ No newline at end of file From ae723af091cb7bf2e61c4cd55f28b1bf84e5b31b Mon Sep 17 00:00:00 2001 From: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> Date: Fri, 23 Dec 2022 13:31:22 -0800 Subject: [PATCH 3/4] Update website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- .../02-Dec-2022/private-packages-clone-git-token.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md b/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md index 9ccd137c03b..62912567893 100644 --- a/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md +++ b/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md @@ -5,7 +5,7 @@ sidebar_label: "Deprecation: Private packages must be cloned using access tokens tags: [Dec-23-2022] --- -The supported way for cloning private GitHub packages is to use the [git token method](/docs/build/packages#git-token-method), where an appropriate access token is passed into the package repository URL with an environment variable. +The supported method for cloning private GitHub packages is the [git token method](/docs/build/packages#git-token-method), where an appropriate access token is passed into the package repository URL with an environment variable. There is a small number of people that has been able to clone private packages using dbt's native GitHub application without explicitly providing an access token. This functionality is being deprecated as it’s limited in flexibility. From d0c2d33c7563acbcaddedcedcdd2663eca97cf8c Mon Sep 17 00:00:00 2001 From: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> Date: Fri, 23 Dec 2022 13:31:31 -0800 Subject: [PATCH 4/4] Update website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- .../02-Dec-2022/private-packages-clone-git-token.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md b/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md index 62912567893..294a4dc55b4 100644 --- a/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md +++ b/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md @@ -7,7 +7,7 @@ tags: [Dec-23-2022] The supported method for cloning private GitHub packages is the [git token method](/docs/build/packages#git-token-method), where an appropriate access token is passed into the package repository URL with an environment variable. -There is a small number of people that has been able to clone private packages using dbt's native GitHub application without explicitly providing an access token. This functionality is being deprecated as it’s limited in flexibility. +A small number of people have been able to clone private packages using dbt's native GitHub application without explicitly providing an access token. This functionality is being deprecated as it’s limited in flexibility. If you have been using a package hosted in a private repository on GitHub, you must start passing an access token into the URL.