Metadata-Version: 2.1
Name: dbt-coves
Version: 1.0.4a3
Summary: CLI tool for dbt users adopting analytics engineering best practices.
Home-page: https://datacoves.com
License: Apache 2.0
Keywords: data engineering,analytics engineering,dbt,ETL,data modelling
Author: Datacoves
Author-email: hello@datacoves.com
Requires-Python: >=3.7,<3.10
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Information Technology
Classifier: License :: OSI Approved :: Apache Software License
Classifier: License :: Other/Proprietary License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Topic :: Software Development :: Build Tools
Classifier: Topic :: Software Development :: Code Generators
Requires-Dist: Jinja2 (>=2.11.2,<2.12.0)
Requires-Dist: PyYAML (>=5.4.1)
Requires-Dist: click (>=8.0.3,<9.0.0)
Requires-Dist: cookiecutter (>=1.7.3,<2.0.0)
Requires-Dist: dbt-bigquery (>=1.0.0,<2.0.0)
Requires-Dist: dbt-core (>=0.18.0,<2.0.0)
Requires-Dist: dbt-redshift (>=1.0.0,<2.0.0)
Requires-Dist: dbt-snowflake (>=1.0.0,<2.0.0)
Requires-Dist: luddite (>=1.0.1,<2.0.0)
Requires-Dist: packaging (>=20.8,<21.0)
Requires-Dist: pre-commit (>=2.15.0,<3.0.0)
Requires-Dist: pretty-errors (>=1.2.19,<2.0.0)
Requires-Dist: pydantic (>=1.8,<2.0)
Requires-Dist: pyfiglet (>=0.8.post1,<0.9)
Requires-Dist: python-slugify (<5.0.0)
Requires-Dist: questionary (>=1.9.0,<2.0.0)
Requires-Dist: rich (>=10.4.0,<11.0.0)
Requires-Dist: sqlfluff (>=0.9.1)
Requires-Dist: sqlfluff-templater-dbt (>=0.9.1)
Requires-Dist: yamlloader (>=1.0.0,<2.0.0)
Project-URL: Documentation, https://datacoves.gitbook.io/dbt-coves/
Project-URL: Repository, https://github.com/datacoves/dbt-coves
Description-Content-Type: text/x-rst


dbt-coves
*********

|Maintenance| |PyPI version fury.io| |Code Style| |Checked with mypy| |Imports: isort| |Imports: python| |Build| |pre-commit.ci status| |codecov| |Maintainability| |Downloads|

.. |Maintenance| image:: https://img.shields.io/badge/Maintained%3F-yes-green.svg
   :target: https://github.com/datacoves/dbt-coves/graphs/commit-activity

.. |PyPI version fury.io| image:: https://badge.fury.io/py/dbt-coves.svg
   :target: https://pypi.python.org/pypi/dbt-coves/

.. |Code Style| image:: https://img.shields.io/badge/code%20style-black-000000.svg
   :target: https://github.com/ambv/black

.. |Checked with mypy| image:: http://www.mypy-lang.org/static/mypy_badge.svg
   :target: http://mypy-lang.org

.. |Imports: isort| image:: https://img.shields.io/badge/%20imports-isort-%231674b1?style=flat&labelColor=ef8336
   :target: https://pycqa.github.io/isort/

.. |Imports: python| image:: https://img.shields.io/badge/python-3.8%20%7C%203.9-blue
   :target: https://img.shields.io/badge/python-3.8%20%7C%203.9-blue

.. |Build| image:: https://github.com/datacoves/dbt-coves/actions/workflows/main_ci.yml/badge.svg
   :target: https://github.com/datacoves/dbt-coves/actions/workflows/main_ci.yml/badge.svg

.. |pre-commit.ci status| image:: https://results.pre-commit.ci/badge/github/bitpicky/dbt-coves/main.svg
   :target: https://results.pre-commit.ci/latest/github/datacoves/dbt-coves/main

.. |codecov| image:: https://codecov.io/gh/datacoves/dbt-coves/branch/main/graph/badge.svg?token=JB0E0LZDW1
   :target: https://codecov.io/gh/datacoves/dbt-coves

.. |Maintainability| image:: https://api.codeclimate.com/v1/badges/1e6a887de605ef8e0eca/maintainability
   :target: https://codeclimate.com/github/datacoves/dbt-coves/maintainability

.. |Downloads| image:: https://pepy.tech/badge/dbt-coves
   :target: https://pepy.tech/project/dbt-coves

What is dbt-coves?
==================

dbt-coves is a complimentary CLI tool for `dbt <https://www.getdbt.com>`_ that allows users to quickly apply `Analytics Engineering <https://www.getdbt.com/what-is-analytics-engineering/>`_ best practices.

dbt-coves helps with the generation of scaffold for dbt by analyzing your data warehouse schema in Redshift, Snowflake, or Big Query and creating the necessary configuration files (sql and yml).

⚠️ **dbt-coves is in alpha version. Don’t use on your prod models unless you have tested it before.**

Here's the tool in action
-------------------------

.. image:: https://cdn.loom.com/sessions/thumbnails/74062cf71cbe4898805ca508ea2d9455-1624905546029-with-play.gif
   :target: https://www.loom.com/share/74062cf71cbe4898805ca508ea2d9455

Supported dbt versions
======================

.. list-table::
   :header-rows: 1

   * - Version
     - Status
   * - <= 0.17.0
     - ❌ Not supported
   * - 0.18.x - 0.21x
     - ✅ Tested
   * - 1.x
     - ✅ Tested

Supported adapters
==================

.. list-table::
   :header-rows: 1

   * - Feature
     - Snowflake
     - Redshift
     - BigQuery
     - Postgres
   * - profile.yml generation
     - ✅ Tested
     - 🕥 In progress
     - ❌ Not tested
     - ❌ Not tested
   * - sources generation
     - ✅ Tested
     - 🕥 In progress
     - ❌ Not tested
     - ❌ Not tested

Installation
************

.. code:: console

   pip install dbt-coves

We recommend using `python virtualenvs
<https://docs.python.org/3/tutorial/venv.html>`_ and create one
separate environment per project.

⚠️ **if you have dbt < 0.18.0 installed, dbt-coves will automatically
upgrade dbt to the latest version**


Main Features
*************


Project initialization
======================

.. code:: console

   dbt-coves init

Initializes a new ready-to-use dbt project that includes recommended
integrations such as `sqlfluff
<https://github.com/sqlfluff/sqlfluff>`_, `pre-commit
<https://pre-commit.com/>`_, dbt packages, among others.

Uses a `cookiecutter <https://github.com/datacoves/cookiecutter-dbt>`_
template to make it easier to maintain.


Models generation
=================

.. code:: console

   dbt-coves generate <resource>

Where *<resource>* could be *sources*.

Code generation tool to easily generate models and model properties
based on configuration and existing data.

Supports `Jinja <https://jinja.palletsprojects.com/>`_ templates to
adjust how the resources are generated.


Metadata
--------

Supports the argument *–metadata* which allows to specify a csv file
containing field types and descriptions to be inserted into the model
property files.

.. code:: console

   dbt-coves generate sources --metadata metadata.csv

Metadata format:

+----------------+----------------+----------------+----------------+----------------+----------------+----------------+
| database       | schema         | relation       | column         | key            | type           | description    |
+================+================+================+================+================+================+================+
| raw            | master         | person         | name           | (empty)        | varchar        | The full name  |
+----------------+----------------+----------------+----------------+----------------+----------------+----------------+
| raw            | master         | person         | name           | groupName      | varchar        | The group name |
+----------------+----------------+----------------+----------------+----------------+----------------+----------------+


Quality Assurance
=================

.. code:: console

   dbt-coves check

Runs a set of checks in your local environment to ensure high code
quality.

Checks can be extended by implementing `pre-commit hooks
<https://pre-commit.com/#creating-new-hooks>`_.


Environment setup
=================

.. code:: console

   dbt-coves setup

Runs a set of checks in your local environment and helps you configure
it properly: ssh key, git, dbt profiles.yml, vscode extensions.


Extract configuration from Airbyte
==================================

.. code:: console

   dbt-coves extract airbyte

Extracts the configuration from your Airbyte sources, connections and
destinations (excluding credentials) and stores it in the specified
folder. The main goal of this feature is to keep track of the
configuration changes in your git repo, and rollback to a specific
version when needed.


Load configuration to Airbyte
=============================

.. code:: console

   dbt-coves load airbyte

Loads the Airbyte configuration generated with *dbt-coves extract
airbyte* on an Airbyte server. Secrets folder needs to be specified
separatedly. You can use `git-secret <https://git-secret.io/>`_ to
encrypt them and make them part of your git repo.


Settings
********

Dbt-coves could optionally read settings from ``.dbt_coves.yml`` or
``.dbt_coves/config.yml``. A standard settings files could looke like
this:

.. code:: yaml

   generate:
     sources:
       schemas:
         - RAW
       destination: "models/sources/{{ schema }}/{{ relation }}.sql"
       model_props_strategy: one_file_per_model
       templates_folder: ".dbt_coves/templates"

In this example options for the ``generate`` command are provided:

``schemas``: List of schema names where to look for source tables

``destination``: Path to generated model, where ``schema`` represents
the lowercased schema and ``relation`` the lowercased table name.

``model_props_strategy``: Defines how dbt-coves generates model
properties files, currently just ``one_file_per_model`` is available,
creates one yaml file per model.

``templates_folder``: Folder where source generation jinja templates
are located.


Override source generation templates
====================================

Customizing generated models and model properties requires placing
specific files under the ``templates_folder`` folder like these:


source_model.sql
----------------

.. code:: sql

   with raw_source as (

       select
           *
       from {% raw %}{{{% endraw %} source('{{ relation.schema.lower() }}', '{{ relation.name.lower() }}') {% raw %}}}{% endraw %}

   ),

   final as (

       select
   {%- if adapter_name == 'SnowflakeAdapter' %}
   {%- for key, cols in nested.items() %}
     {%- for col in cols %}
           {{ key }}:{{ '"' + col + '"' }}::{{ cols[col]["type"] }} as {{ cols[col]["id"] }}{% if not loop.last or columns %},{% endif %}
     {%- endfor %}
   {%- endfor %}
   {%- elif adapter_name == 'BigQueryAdapter' %}
   {%- for key, cols in nested.items() %}
     {%- for col in cols %}
           cast({{ key }}.{{ col }} as {{ cols[col]["type"].replace("varchar", "string") }}) as {{ cols[col]["id"] }}{% if not loop.last or columns %},{% endif %}
     {%- endfor %}
   {%- endfor %}
   {%- elif adapter_name == 'RedshiftAdapter' %}
   {%- for key, cols in nested.items() %}
     {%- for col in cols %}
           {{ key }}.{{ col }}::{{ cols[col]["type"] }} as {{ cols[col]["id"] }}{% if not loop.last or columns %},{% endif %}
     {%- endfor %}
   {%- endfor %}
   {%- endif %}
   {%- for col in columns %}
           {{ '"' + col.name + '"' }} as {{ col.name.lower() }}{% if not loop.last %},{% endif %}
   {%- endfor %}

       from raw_source

   )

   select * from final


source_model_props.yml
----------------------

.. code:: yaml

   version: 2

   sources:
     - name: {{ relation.schema.lower() }}
   {%- if source_database %}
       database: {{ source_database }}
   {%- endif %}
       schema: {{ relation.schema.lower() }}
       tables:
         - name: {{ relation.name.lower() }}
           identifier: {{ relation.name }}

   models:
     - name: {{ model.lower() }}
       columns:
   {%- for cols in nested.values() %}
     {%- for col in cols %}
         - name: {{ cols[col]["id"] }}
         {%- if cols[col]["description"] %}
           description: "{{ cols[col]['description'] }}"
         {%- endif %}
     {%- endfor %}
   {%- endfor %}
   {%- for col in columns %}
         - name: {{ col.name.lower() }}
   {%- endfor %}


CLI Detailed Reference
**********************

CLI tool for dbt users applying analytics engineering best practices.

::

   usage: dbt_coves [-h] [-v] {init,generate,check,fix,setup,extract,load} ...


Named Arguments
===============

-v, --version

show program’s version number and exit


dbt-coves commands
==================

task

Possible choices: init, generate, check, fix, setup, extract, load


Sub-commands:
=============


init
----

Initializes a new dbt project using predefined conventions.

::

   dbt_coves init [-h] [--log-level LOG_LEVEL] [-vv] [--config-path CONFIG_PATH] [--project-dir PROJECT_DIR] [--profiles-dir PROFILES_DIR] [--profile PROFILE] [-t TARGET] [--vars VARS] [--template TEMPLATE] [--current-dir]


Named Arguments
~~~~~~~~~~~~~~~

--log-level

overrides default log level

Default: “”

-vv, --verbose

When provided the length of the tracebacks will not be truncated.

Default: False

--config-path

Full path to .dbt_coves.yml file if not using default. Default is
current working directory.

--project-dir

Which directory to look in for the dbt_project.yml file. Default is
the current working directory and its parents.

--profiles-dir

Which directory to look in for the profiles.yml file.

Default: “~/.dbt”

--profile

Which profile to load. Overrides setting in dbt_project.yml.

-t, --target

Which target to load for the given profile

--vars

Supply variables to your dbt_project.yml file. This argument should be
a YAML string, eg. ‘{my_variable: my_value}’

Default: “{}”

--template

Cookiecutter template github url, i.e.
‘https://github.com/datacoves/cookiecutter-dbt-coves.git’

--current-dir

Generate the dbt project in the current directory.

Default: False


generate
--------

Generates sources and models with defaults.

::

   dbt_coves generate [-h] [--log-level LOG_LEVEL] [-vv] [--config-path CONFIG_PATH] [--project-dir PROJECT_DIR] [--profiles-dir PROFILES_DIR] [--profile PROFILE] [-t TARGET] [--vars VARS] {sources} ...


Named Arguments
~~~~~~~~~~~~~~~

--log-level

overrides default log level

Default: “”

-vv, --verbose

When provided the length of the tracebacks will not be truncated.

Default: False

--config-path

Full path to .dbt_coves.yml file if not using default. Default is
current working directory.

--project-dir

Which directory to look in for the dbt_project.yml file. Default is
the current working directory and its parents.

--profiles-dir

Which directory to look in for the profiles.yml file.

Default: “~/.dbt”

--profile

Which profile to load. Overrides setting in dbt_project.yml.

-t, --target

Which target to load for the given profile

--vars

Supply variables to your dbt_project.yml file. This argument should be
a YAML string, eg. ‘{my_variable: my_value}’

Default: “{}”


dbt-coves generate commands
~~~~~~~~~~~~~~~~~~~~~~~~~~~

task

Possible choices: sources


Sub-commands:
~~~~~~~~~~~~~


sources
"""""""

Generate source dbt models by inspecting the database schemas and
relations.

::

   dbt_coves generate sources [-h] [--log-level LOG_LEVEL] [-vv] [--config-path CONFIG_PATH] [--project-dir PROJECT_DIR] [--profiles-dir PROFILES_DIR] [--profile PROFILE] [-t TARGET] [--vars VARS] [--database DATABASE] [--schemas SCHEMAS]
                              [--relations RELATIONS] [--destination DESTINATION] [--model_props_strategy MODEL_PROPS_STRATEGY] [--templates_folder TEMPLATES_FOLDER] [--metadata METADATA]


Named Arguments
+++++++++++++++

--log-level

overrides default log level

Default: “”

-vv, --verbose

When provided the length of the tracebacks will not be truncated.

Default: False

--config-path

Full path to .dbt_coves.yml file if not using default. Default is
current working directory.

--project-dir

Which directory to look in for the dbt_project.yml file. Default is
the current working directory and its parents.

--profiles-dir

Which directory to look in for the profiles.yml file.

Default: “~/.dbt”

--profile

Which profile to load. Overrides setting in dbt_project.yml.

-t, --target

Which target to load for the given profile

--vars

Supply variables to your dbt_project.yml file. This argument should be
a YAML string, eg. ‘{my_variable: my_value}’

Default: “{}”

--database

Database where source relations live, if different than target

--schemas

Comma separated list of schemas where raw data resides, i.e.
‘RAW_SALESFORCE,RAW_HUBSPOT’

--relations

Comma separated list of relations where raw data resides, i.e.
‘RAW_HUBSPOT_PRODUCTS,RAW_SALESFORCE_USERS’

--destination

Where models sql files will be generated, i.e.
‘models/{schema_name}/{relation_name}.sql’

--model_props_strategy

Strategy for model properties files generation, i.e.
‘one_file_per_model’

--templates_folder

Folder with jinja templates that override default sources generation
templates, i.e. ‘templates’

--metadata

Path to csv file containing metadata, i.e. ‘metadata.csv’


check
-----

Runs pre-commit hooks and linters.

::

   dbt_coves check [-h] [--log-level LOG_LEVEL] [-vv] [--config-path CONFIG_PATH] [--project-dir PROJECT_DIR] [--profiles-dir PROFILES_DIR] [--profile PROFILE] [-t TARGET] [--vars VARS] [--no-fix]


Named Arguments
~~~~~~~~~~~~~~~

--log-level

overrides default log level

Default: “”

-vv, --verbose

When provided the length of the tracebacks will not be truncated.

Default: False

--config-path

Full path to .dbt_coves.yml file if not using default. Default is
current working directory.

--project-dir

Which directory to look in for the dbt_project.yml file. Default is
the current working directory and its parents.

--profiles-dir

Which directory to look in for the profiles.yml file.

Default: “~/.dbt”

--profile

Which profile to load. Overrides setting in dbt_project.yml.

-t, --target

Which target to load for the given profile

--vars

Supply variables to your dbt_project.yml file. This argument should be
a YAML string, eg. ‘{my_variable: my_value}’

Default: “{}”

--no-fix

Do not suggest auto-fixing linting errors. Useful when running this
command on CI jobs.

Default: False


fix
---

Runs linter fixes.

::

   dbt_coves fix [-h] [--log-level LOG_LEVEL] [-vv] [--config-path CONFIG_PATH] [--project-dir PROJECT_DIR] [--profiles-dir PROFILES_DIR] [--profile PROFILE] [-t TARGET] [--vars VARS]


Named Arguments
~~~~~~~~~~~~~~~

--log-level

overrides default log level

Default: “”

-vv, --verbose

When provided the length of the tracebacks will not be truncated.

Default: False

--config-path

Full path to .dbt_coves.yml file if not using default. Default is
current working directory.

--project-dir

Which directory to look in for the dbt_project.yml file. Default is
the current working directory and its parents.

--profiles-dir

Which directory to look in for the profiles.yml file.

Default: “~/.dbt”

--profile

Which profile to load. Overrides setting in dbt_project.yml.

-t, --target

Which target to load for the given profile

--vars

Supply variables to your dbt_project.yml file. This argument should be
a YAML string, eg. ‘{my_variable: my_value}’

Default: “{}”


setup
-----

Sets up SSH keys, git repo, and db connections.

::

   dbt_coves setup [-h] [--log-level LOG_LEVEL] [-vv] [--config-path CONFIG_PATH] [--project-dir PROJECT_DIR] [--profiles-dir PROFILES_DIR] [--profile PROFILE] [-t TARGET] [--vars VARS]


Named Arguments
~~~~~~~~~~~~~~~

--log-level

overrides default log level

Default: “”

-vv, --verbose

When provided the length of the tracebacks will not be truncated.

Default: False

--config-path

Full path to .dbt_coves.yml file if not using default. Default is
current working directory.

--project-dir

Which directory to look in for the dbt_project.yml file. Default is
the current working directory and its parents.

--profiles-dir

Which directory to look in for the profiles.yml file.

Default: “~/.dbt”

--profile

Which profile to load. Overrides setting in dbt_project.yml.

-t, --target

Which target to load for the given profile

--vars

Supply variables to your dbt_project.yml file. This argument should be
a YAML string, eg. ‘{my_variable: my_value}’

Default: “{}”


extract
-------

Extracts data from different systems.

::

   dbt_coves extract [-h] [--log-level LOG_LEVEL] [-vv] [--config-path CONFIG_PATH] [--project-dir PROJECT_DIR] [--profiles-dir PROFILES_DIR] [--profile PROFILE] [-t TARGET] [--vars VARS] {airbyte} ...


Named Arguments
~~~~~~~~~~~~~~~

--log-level

overrides default log level

Default: “”

-vv, --verbose

When provided the length of the tracebacks will not be truncated.

Default: False

--config-path

Full path to .dbt_coves.yml file if not using default. Default is
current working directory.

--project-dir

Which directory to look in for the dbt_project.yml file. Default is
the current working directory and its parents.

--profiles-dir

Which directory to look in for the profiles.yml file.

Default: “~/.dbt”

--profile

Which profile to load. Overrides setting in dbt_project.yml.

-t, --target

Which target to load for the given profile

--vars

Supply variables to your dbt_project.yml file. This argument should be
a YAML string, eg. ‘{my_variable: my_value}’

Default: “{}”


dbt-coves extract commands
~~~~~~~~~~~~~~~~~~~~~~~~~~

task

Possible choices: airbyte


Sub-commands:
~~~~~~~~~~~~~


airbyte
"""""""

Extracts airbyte sources, connections and destinations and stores them
as json files

::

   dbt_coves extract airbyte [-h] [--log-level LOG_LEVEL] [-vv] [--config-path CONFIG_PATH] [--project-dir PROJECT_DIR] [--profiles-dir PROFILES_DIR] [--profile PROFILE] [-t TARGET] [--vars VARS] [--path PATH] [--host HOST] [--port PORT]
                             [--dbt_list_args DBT_LIST_ARGS]


Named Arguments
+++++++++++++++

--log-level

overrides default log level

Default: “”

-vv, --verbose

When provided the length of the tracebacks will not be truncated.

Default: False

--config-path

Full path to .dbt_coves.yml file if not using default. Default is
current working directory.

--project-dir

Which directory to look in for the dbt_project.yml file. Default is
the current working directory and its parents.

--profiles-dir

Which directory to look in for the profiles.yml file.

Default: “~/.dbt”

--profile

Which profile to load. Overrides setting in dbt_project.yml.

-t, --target

Which target to load for the given profile

--vars

Supply variables to your dbt_project.yml file. This argument should be
a YAML string, eg. ‘{my_variable: my_value}’

Default: “{}”

--path

Where json files will be generated, i.e. ‘airbyte’

--host

Airbyte’s API hostname, i.e. ‘http://airbyte-server’

--port

Airbyte’s API port, i.e. ‘8001’

--dbt_list_args

Extra dbt arguments, selectors or modifiers


load
----

Loads data from different systems.

::

   dbt_coves load [-h] [--log-level LOG_LEVEL] [-vv] [--config-path CONFIG_PATH] [--project-dir PROJECT_DIR] [--profiles-dir PROFILES_DIR] [--profile PROFILE] [-t TARGET] [--vars VARS] {airbyte} ...


Named Arguments
~~~~~~~~~~~~~~~

--log-level

overrides default log level

Default: “”

-vv, --verbose

When provided the length of the tracebacks will not be truncated.

Default: False

--config-path

Full path to .dbt_coves.yml file if not using default. Default is
current working directory.

--project-dir

Which directory to look in for the dbt_project.yml file. Default is
the current working directory and its parents.

--profiles-dir

Which directory to look in for the profiles.yml file.

Default: “~/.dbt”

--profile

Which profile to load. Overrides setting in dbt_project.yml.

-t, --target

Which target to load for the given profile

--vars

Supply variables to your dbt_project.yml file. This argument should be
a YAML string, eg. ‘{my_variable: my_value}’

Default: “{}”


dbt-coves load commands
~~~~~~~~~~~~~~~~~~~~~~~

task

Possible choices: airbyte


Sub-commands:
~~~~~~~~~~~~~


airbyte
"""""""

Extracts airbyte sources, connections and destinations and stores them
as json files

::

   dbt_coves load airbyte [-h] [--log-level LOG_LEVEL] [-vv] [--config-path CONFIG_PATH] [--project-dir PROJECT_DIR] [--profiles-dir PROFILES_DIR] [--profile PROFILE] [-t TARGET] [--vars VARS] [--path PATH] [--host HOST] [--port PORT]
                          [--secrets SECRETS]


Named Arguments
+++++++++++++++

--log-level

overrides default log level

Default: “”

-vv, --verbose

When provided the length of the tracebacks will not be truncated.

Default: False

--config-path

Full path to .dbt_coves.yml file if not using default. Default is
current working directory.

--project-dir

Which directory to look in for the dbt_project.yml file. Default is
the current working directory and its parents.

--profiles-dir

Which directory to look in for the profiles.yml file.

Default: “~/.dbt”

--profile

Which profile to load. Overrides setting in dbt_project.yml.

-t, --target

Which target to load for the given profile

--vars

Supply variables to your dbt_project.yml file. This argument should be
a YAML string, eg. ‘{my_variable: my_value}’

Default: “{}”

--path

Where json files will be loaded from, i.e. ‘/var/data’

--host

Airbyte’s API hostname, i.e. ‘http://airbyte-server’

--port

Airbyte’s API port, i.e. ‘8001’

--secrets

Secret files location for Airbyte configuration, i.e. ‘./secrets’

Select one of the available sub-commands with –help to find out more
about them.


Thanks
******

The project main structure was inspired by `dbt-sugar
<https://github.com/bitpicky/dbt-sugar>`_. Special thanks to `Bastien
Boutonnet <https://github.com/bastienboutonnet>`_ for the great work
done.


Authors
*******

*  Sebastian Sassi `@sebasuy <https://twitter.com/sebasuy>`_ –
   `Convexa <https://convexa.ai>`_

*  Noel Gomez `@noel_g <https://twitter.com/noel_g>`_ – `Ninecoves
   <https://ninecoves.com>`_


About
*****

Learn more about `Datacoves <https://datacoves.com>`_.

