15704ab3d5
* replace dbt/common with dbt-common * update requirements, remove colorama * remove dbt-common unit tests * WIP * some cleanup * update imports from dbt.common to dbt_common * remove tests/unit/common * changelog entry * remove commented out code * move cache exceptions to dbt/adapters (#9361) * point to dbt-common main * Move the contents of dbt.contracts.results to a new dbt.artifacts directory (#9350) * conflict resolution cleanup * cleanup * add ignoreb --------- Co-authored-by: Michelle Ark <michelle.ark@dbtlabs.com> Co-authored-by: Michelle Ark <MichelleArk@users.noreply.github.com> Co-authored-by: Gerda Shank <gerda@dbtlabs.com>
1.4 KiB
Deps README
The deps module is responsible for installing dbt packages into dbt projects. A dbt package is a standalone dbt project with models and macros that solve a specific problem area. More specific information on dbt packages is available on the docs site.
What's a package?
See How do I specify a package? on the docs site for a detailed explination of the different types of packages supported and expected formats.
Files
base.py
Defines the base classes of PinnedPackage and UnpinnedPackage.
downloads_directory sets the directory packages will be downloaded to.
_install has retry logic if the download or untarring process hit exceptions (see dbt_common.utils.connection_exception_retry).
git.py
Extends PinnedPackage and UnpinnedPackage specific to dbt packages defined with git urls.
local.py
Extends PinnedPackage and UnpinnedPackage specific to dbt packages defined locally.
registry.py
Extends PinnedPackage and UnpinnedPackage specific to dbt packages defined on the dbt Hub registry.
resolver.py
Resolves the package definition into package objects to download.
tarball.py
Extends PinnedPackage and UnpinnedPackage specific to dbt packages defined by a URL to a tarball hosted on an HTTP server.