Timle/dbt deps tarball (branch rename)

[timle2]

Continued from
#4689

Continued from
#4220

Revision 3 added Nov 6 2022

in support of Issue [Feature] add new dbt.deps type: url to internally hosted tarball #4205

Proposed solution for feature request 4205

Description

Enable direct linking to tarball urls in packages.yml, for example:

# manufactured test, since you'd want to use hub to install these 
# public tarball used here as example only! 
# this would usually be a tarball hosted  on an internal network
packages:
  - tarball: https://codeload.github.com/dbt-labs/dbt-utils/tar.gz/0.6.5
    name: 'dbt_utils_065'
    version: 0.6.5

  - tarball: https://codeload.github.com/dbt-labs/dbt-utils/tar.gz/0.6.4
    name: 'dbt_utils'
    version: 0.9.2

Rational:

• dbt projects being self hosted on larger enterprise environments often don't have a connection to the internet (dbt hubs won't work).
• dbt users on larger enterprise environments like to build internal private packages for non-public use (help out other dbt users in company with specific functionality)
• git package install is not a good option at scale for larger enterprise environments
• internal file hosting service (such as internal artifactory service or internal cloud storage buckets) can be easily configured to host packages for install during deployment, so lets give dbt users a way to install from a direct tar file link

Sketching out doc changes here:
https://github.com/timle2/docs.getdbt.com/blob/dbt-docs-tarball-package-updates/website/docs/docs/building-a-dbt-project/package-management.md#tar-files

Checklist

• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• [TODO] I have updated the CHANGELOG.md and added information about my change

[timle2]

debugging #4689 where it was suggested that I try a different branch name

[timle2]

thanks for the assist here @dbeatty10 - looks like #4689 has started to run the tests properly again. Should I continue the PR here (new location, update branch name) or resume at #4689 (original location, original branch name)?

[dbeatty10]

@timle2 awesome you got it working again!

You can close this one and resume with the original pull request location and original branch name.