DbtCLI

yaml

type: "io.kestra.plugin.dbt.cli.DbtCLI"

Execute dbt CLI commands.

Examples

Launch a dbt build command on a sample dbt project hosted on GitHub.

yaml

id: dbt_build
namespace: company.team

tasks:
  - id: dbt
    type: io.kestra.plugin.core.flow.WorkingDirectory
    tasks:
      - id: cloneRepository
        type: io.kestra.plugin.git.Clone
        url: https://github.com/kestra-io/dbt-example
        branch: main

      - id: dbt-build
        type: io.kestra.plugin.dbt.cli.DbtCLI
        containerImage: ghcr.io/kestra-io/dbt-duckdb:latest
        taskRunner:
          type: io.kestra.plugin.scripts.runner.docker.Docker
        commands:
          - dbt build
        profiles: |
          my_dbt_project:
            outputs:
              dev:
                type: duckdb
                path: ":memory:"
            target: dev

Sync dbt project files from a specific GitHub branch to Kestra's Namespace Files and run dbt build command. Note that we exclude the profiles.yml file because the profiles is defined in the dbt task directly. This exclude pattern is useful if you want to override the profiles.yml file by defining it in the dbt task. In this example, the profiles.yml was initially targeting a dev environment, but we override it to target a prod environment.

yaml

id: dbt_build
namespace: company.team

tasks:
  - id: sync
    type: io.kestra.plugin.git.SyncNamespaceFiles
    url: https://github.com/kestra-io/dbt-example
    branch: master
    namespace: "{{ flow.namespace }}"
    gitDirectory: dbt
    dryRun: false

  - id: dbt_build
    type: io.kestra.plugin.dbt.cli.DbtCLI
    containerImage: ghcr.io/kestra-io/dbt-duckdb:latest
    namespaceFiles:
      enabled: true
      exclude:
        - profiles.yml
    taskRunner:
      type: io.kestra.plugin.scripts.runner.docker.Docker
    commands:
      - dbt build
    profiles: |
      my_dbt_project:
        outputs:
          prod:
            type: duckdb
            path: ":memory:"
            schema: main
            threads: 8
        target: prod

Install a custom dbt version and run dbt deps and dbt build commands. Note how you can also configure the memory limit for the Docker runner. This is useful when you see Zombie processes.

yaml

id: dbt_custom_dependencies
namespace: company.team

inputs:
  - id: dbt_version
    type: STRING
    defaults: "dbt-duckdb==1.6.0"

tasks:
  - id: git
    type: io.kestra.plugin.core.flow.WorkingDirectory
    tasks:
      - id: clone_repository
        type: io.kestra.plugin.git.Clone
        url: https://github.com/kestra-io/dbt-example
        branch: main

      - id: dbt
        type: io.kestra.plugin.dbt.cli.DbtCLI
        taskRunner:
          type: io.kestra.plugin.scripts.runner.docker.Docker
          memory:
            memory: 1GB
        containerImage: python:3.11-slim
        beforeCommands:
          - pip install uv
          - uv venv --quiet
          - . .venv/bin/activate --quiet
          - uv pip install --quiet {{ inputs.dbt_version }}
        commands:
          - dbt deps
          - dbt build
        profiles: |
          my_dbt_project:
            outputs:
              dev:
                type: duckdb
                path: ":memory:"
                fixed_retries: 1
                threads: 16
                timeout_seconds: 300
            target: dev

Clone a Git repository and build dbt models. Note that, as the dbt project files are in a separate directory, you need to set the projectDir task property and use --project-dir in each dbt CLI command.

yaml

id: dwh_and_analytics
namespace: company.team

tasks:
  - id: dbt
    type: io.kestra.plugin.core.flow.WorkingDirectory
    tasks:
    - id: clone_repository
      type: io.kestra.plugin.git.Clone
      url: https://github.com/kestra-io/dbt-example
      branch: master

    - id: dbt_build
      type: io.kestra.plugin.dbt.cli.DbtCLI
      taskRunner:
        type: io.kestra.plugin.scripts.runner.docker.Docker
      containerImage: ghcr.io/kestra-io/dbt-duckdb:latest
      commands:
        - dbt deps --project-dir dbt --target prod
        - dbt build --project-dir dbt --target prod
      projectDir: dbt
      profiles: |
        my_dbt_project:
          outputs:
            dev:
              type: duckdb
              path: dbt.duckdb
              extensions:
                - parquet
              fixed_retries: 1
              threads: 16
              timeout_seconds: 300
            prod:
              type: duckdb
              path: dbt2.duckdb
              extensions: 
                - parquet
              fixed_retries: 1
              threads: 16
              timeout_seconds: 300
          target: dev

Clone a Git repository and build dbt models using the --defer flag. The loadManifest property will fetch an existing manifest.json and use it to run a subset of models that have changed since the last run.

yaml

id: dbt_defer
namespace: company.team
inputs:
  - id: dbt_command
    type: SELECT
    allowCustomValue: true
    defaults: dbt build --project-dir dbt --target prod --no-partial-parse
    values:
      - dbt build --project-dir dbt --target prod --no-partial-parse
      - dbt build --project-dir dbt --target prod --no-partial-parse --select state:modified+ --defer --state ./target

tasks:
  - id: dbt
    type: io.kestra.plugin.core.flow.WorkingDirectory
    tasks:
      - id: clone_repository
        type: io.kestra.plugin.git.Clone
        url: https://github.com/kestra-io/dbt-example
        branch: master

      - id: dbt_build
        type: io.kestra.plugin.dbt.cli.DbtCLI
        taskRunner:
          type: io.kestra.plugin.scripts.runner.docker.Docker
          delete: true
        containerImage: ghcr.io/kestra-io/dbt-duckdb:latest
        loadManifest:
          key: manifest.json
          namespace: "{{ flow.namespace }}"
        storeManifest:
          key: manifest.json
          namespace: "{{ flow.namespace }}"
        projectDir: dbt
        commands:
          - "{{ inputs.dbt_command }}"
        profiles: |
          my_dbt_project:
            outputs:
              dev:
                type: duckdb
                path: ":memory:"
                fixed_retries: 1
                threads: 16
                timeout_seconds: 300
              prod:
                type: duckdb
                path: dbt2.duckdb
                extensions:
                  - parquet
                fixed_retries: 1
                threads: 16
                timeout_seconds: 300
            target: dev

Properties

`commands`

Type: array
SubType: string
Dynamic: ✔️
Required: ✔️
Min items: 1

The list of dbt CLI commands to run.

`interpreter`

Type: array
SubType: string
Dynamic: ❌
Required: ✔️
Default: [/bin/sh, -c]
Min items: 1

Which interpreter to use.

`warningOnStdErr`

Type: boolean
Dynamic: ❌
Required: ✔️
Default: true

Whether to set the task state to WARNING when any stdErr output is detected.

Note that a script error will set the state to FAILED regardless.

`beforeCommands`

Type: array
SubType: string
Dynamic: ✔️
Required: ❌

A list of commands that will run before the commands, allowing to set up the environment e.g. pip install -r requirements.txt.

`containerImage`

Type: string
Dynamic: ✔️
Required: ❌
Default: ghcr.io/kestra-io/dbt

The task runner container image, only used if the task runner is container-based.

`docker`

⚠ Deprecated

Type: DockerOptions
Dynamic: ❓
Required: ❌

Deprecated - use the 'taskRunner' property instead.

Only used if the taskRunner property is not set

`env`

Type: object
SubType: string
Dynamic: ✔️
Required: ❌

Additional environment variables for the current process.

`failFast`

Type: boolean
Dynamic: ❌
Required: ❌
Default: true

Fail the task on the first command with a non-zero status.

If set to false all commands will be executed one after the other. The final state of task execution is determined by the last command. Note that this property maybe be ignored if a non compatible interpreter is specified. You can also disable it if your interpreter does not support the set -eoption.

`inputFiles`

Type:
- object
- string
Dynamic: ✔️
Required: ❌

The files to create on the local filesystem. It can be a map or a JSON object.

`loadManifest`

Type: DbtCLI-KvStoreManifest
Dynamic: ❓
Required: ❌

Load manifest.

Use this field to retrieve an existing manifest.json in the KV Store and put it in the inputFiles. The manifest.json will be put under ./target/manifest.json or under ./projectDir/target/manifest.json if you specify a projectDir.

`namespaceFiles`

Type: NamespaceFiles
Dynamic: ❌
Required: ❌

Inject namespace files.

Inject namespace files to this task. When enabled, it will, by default, load all namespace files into the working directory. However, you can use the include or exclude properties to limit which namespace files will be injected.

`outputDirectory`

⚠ Deprecated

Type: boolean
Dynamic: ❓
Required: ❌
Default: false

Whether to setup the output directory mechanism.

Required to use the {{ outputDir }} expression. Note that it could increase the starting time. Deprecated, use the outputFiles property instead.

`outputFiles`

Type: array
SubType: string
Dynamic: ✔️
Required: ❌

The files from the local filesystem to send to Kestra's internal storage.

Must be a list of glob expressions relative to the current working directory, some examples: my-dir/**, my-dir/*/** or my-dir/my-file.txt.

`parseRunResults`

Type:
- boolean
- string
Dynamic: ✔️
Required: ❌

`profiles`

Type: string
Dynamic: ✔️
Required: ❌

The profiles.yml file content.

If a profile.yml file already exists in the current working directory, it will be overridden.

`projectDir`

Type: string
Dynamic: ✔️
Required: ❌

The dbt project directory, if it's not the working directory.

To use it, also use this directory in the --project-dir flag on the dbt CLI commands.

`runner`

⚠ Deprecated

Type: string
Dynamic: ❌
Required: ❌
Possible Values:
- PROCESS
- DOCKER

Deprecated - use the 'taskRunner' property instead.

Only used if the taskRunner property is not set

`storeManifest`

Type: DbtCLI-KvStoreManifest
Dynamic: ❓
Required: ❌

Store manifest.

Use this field to persist your manifest.json in the KV Store.

`targetOS`

Type: string
Dynamic: ❓
Required: ❌
Default: AUTO
Possible Values:
- LINUX
- WINDOWS
- AUTO

The target operating system where the script will run.

`taskRunner`

Type: TaskRunner
Dynamic: ❌
Required: ❌
Default: {type=io.kestra.plugin.scripts.runner.docker.Docker, entryPoint=[]}

The task runner to use.

Task runners are provided by plugins, each have their own properties. If you change from the default one, be careful to also configure the entrypoint to an empty list if needed.

Outputs

`exitCode`

Type: integer
Required: ✔️
Default: 0

The exit code of the entire flow execution.

`outputFiles`

Type: object
SubType: string
Required: ❌

The output files' URIs in Kestra's internal storage.

`vars`

Type: object
Required: ❌

The value extracted from the output of the executed commands.

Definitions

`io.kestra.core.models.tasks.NamespaceFiles`

Properties

`enabled`

Type: boolean
Dynamic: ❌
Required: ❌
Default: true

Whether to enable namespace files to be loaded into the working directory. If explicitly set to true in a task, it will load all Namespace Files into the task's working directory. Note that this property is by default set to true so that you can specify only the include and exclude properties to filter the files to load without having to explicitly set enabled to true.

`exclude`

Type: array
SubType: string
Dynamic: ❌
Required: ❌

A list of filters to exclude matching glob patterns. This allows you to exclude a subset of the Namespace Files from being downloaded at runtime. You can combine this property together with include to only inject a subset of files that you need into the task's working directory.

`include`

Type: array
SubType: string
Dynamic: ❌
Required: ❌

A list of filters to include only matching glob patterns. This allows you to only load a subset of the Namespace Files into the working directory.

`io.kestra.plugin.scripts.runner.docker.Cpu`

Properties

`cpus`

Type: integer
Dynamic: ❌
Required: ❌

The maximum amount of CPU resources a container can use.

Make sure to set that to a numeric value e.g. cpus: "1.5" or cpus: "4" or For instance, if the host machine has two CPUs and you set cpus: "1.5", the container is guaranteed at most one and a half of the CPUs.

`io.kestra.core.models.tasks.runners.TaskRunner`

Properties

`type`

Type: string
Dynamic: ❓
Required: ✔️
Validation regExp: \p{javaJavaIdentifierStart}\p{javaJavaIdentifierPart}*(\.\p{javaJavaIdentifierStart}\p{javaJavaIdentifierPart}*)*
Min length: 1

`io.kestra.plugin.scripts.runner.docker.Memory`

Properties

`kernelMemory`

Type: string
Dynamic: ✔️
Required: ❌

The maximum amount of kernel memory the container can use.

The minimum allowed value is 4MB. Because kernel memory cannot be swapped out, a container which is starved of kernel memory may block host machine resources, which can have side effects on the host machine and on other containers. See the kernel-memory docs for more details.

`memory`

Type: string
Dynamic: ✔️
Required: ❌

The maximum amount of memory resources the container can use.

Make sure to use the format number + unit (regardless of the case) without any spaces. The unit can be KB (kilobytes), MB (megabytes), GB (gigabytes), etc.

Given that it's case-insensitive, the following values are equivalent:

"512MB"
"512Mb"
"512mb"
"512000KB"
"0.5GB"

It is recommended that you allocate at least 6MB.

`memoryReservation`

Type: string
Dynamic: ✔️
Required: ❌

Allows you to specify a soft limit smaller than memory which is activated when Docker detects contention or low memory on the host machine.

If you use memoryReservation, it must be set lower than memory for it to take precedence. Because it is a soft limit, it does not guarantee that the container doesn’t exceed the limit.

`memorySwap`

Type: string
Dynamic: ✔️
Required: ❌

The total amount of memory and swap that can be used by a container.

If memory and memorySwap are set to the same value, this prevents containers from using any swap. This is because memorySwap includes both the physical memory and swap space, while memory is only the amount of physical memory that can be used.

`memorySwappiness`

Type: string
Dynamic: ✔️
Required: ❌

A setting which controls the likelihood of the kernel to swap memory pages.

By default, the host kernel can swap out a percentage of anonymous pages used by a container. You can set memorySwappiness to a value between 0 and 100 to tune this percentage.

`oomKillDisable`

Type: boolean
Dynamic: ❌
Required: ❌

By default, if an out-of-memory (OOM) error occurs, the kernel kills processes in a container.

To change this behavior, use the oomKillDisable option. Only disable the OOM killer on containers where you have also set the memory option. If the memory flag is not set, the host can run out of memory, and the kernel may need to kill the host system’s processes to free the memory.

`io.kestra.plugin.dbt.cli.DbtCLI-KvStoreManifest`

Properties

`key`

Type: string
Dynamic: ✔️
Required: ✔️

Key

KV store key containing the manifest.json

`namespace`

Type: string
Dynamic: ✔️
Required: ✔️

Namespace

KV store namespace containing the manifest.json

`io.kestra.plugin.scripts.exec.scripts.models.DockerOptions`

Properties

`image`

Type: string
Dynamic: ✔️
Required: ✔️
Min length: 1

Docker image to use.

`config`

Type:
- string
- object
Dynamic: ✔️
Required: ❌

Docker configuration file.

Docker configuration file that can set access credentials to private container registries. Usually located in ~/.docker/config.json.

`cpu`

Type: Cpu
Dynamic: ❌
Required: ❌

Limits the CPU usage to a given maximum threshold value.

By default, each container’s access to the host machine’s CPU cycles is unlimited. You can set various constraints to limit a given container’s access to the host machine’s CPU cycles.

`credentials`

Type: Credentials
Dynamic: ✔️
Required: ❌

`deviceRequests`

Type: array
SubType: DeviceRequest
Dynamic: ❌
Required: ❌

A list of device requests to be sent to device drivers.

`entryPoint`

Type: array
SubType: string
Dynamic: ✔️
Required: ❌

Docker entrypoint to use.

`extraHosts`

Type: array
SubType: string
Dynamic: ✔️
Required: ❌

Extra hostname mappings to the container network interface configuration.

`host`

Type: string
Dynamic: ✔️
Required: ❌

Docker API URI.

`memory`

Type: Memory
Dynamic: ❌
Required: ❌

Limits memory usage to a given maximum threshold value.

Docker can enforce hard memory limits, which allow the container to use no more than a given amount of user or system memory, or soft limits, which allow the container to use as much memory as it needs unless certain conditions are met, such as when the kernel detects low memory or contention on the host machine. Some of these options have different effects when used alone or when more than one option is set.

`networkMode`

Type: string
Dynamic: ✔️
Required: ❌

Docker network mode to use e.g. host, none, etc.

`pullPolicy`

Type: string
Dynamic: ❌
Required: ❌
Default: ALWAYS
Possible Values:
- IF_NOT_PRESENT
- ALWAYS
- NEVER

The image pull policy for a container image and the tag of the image, which affect when Docker attempts to pull (download) the specified image.

`shmSize`

Type: string
Dynamic: ✔️
Required: ❌

Size of /dev/shm in bytes.

The size must be greater than 0. If omitted, the system uses 64MB.

`user`

Type: string
Dynamic: ✔️
Required: ❌

User in the Docker container.

`volumes`

Type: array
SubType: string
Dynamic: ✔️
Required: ❌

List of volumes to mount.

Must be a valid mount expression as string, example : /home/user:/app.

Volumes mount are disabled by default for security reasons; you must enable them on server configuration by setting kestra.tasks.scripts.docker.volume-enabled to true.

`io.kestra.plugin.scripts.runner.docker.Credentials`

Properties

`auth`

Type: string
Dynamic: ✔️
Required: ❌

The registry authentication.

The auth field is a base64-encoded authentication string of username:password or a token.

`identityToken`

Type: string
Dynamic: ✔️
Required: ❌

The identity token.

`password`

Type: string
Dynamic: ✔️
Required: ❌

The registry password.

`registry`

Type: string
Dynamic: ✔️
Required: ❌

The registry URL.

If not defined, the registry will be extracted from the image name.

`registryToken`

Type: string
Dynamic: ✔️
Required: ❌

The registry token.

`username`

Type: string
Dynamic: ✔️
Required: ❌

The registry username.

`io.kestra.plugin.scripts.runner.docker.DeviceRequest`

Properties

`capabilities`

Type: array
SubType: array
Dynamic: ❌
Required: ❌

A list of capabilities; an OR list of AND lists of capabilities.

`count`

Type: integer
Dynamic: ❌
Required: ❌

`deviceIds`

Type: array
SubType: string
Dynamic: ✔️
Required: ❌

`driver`

Type: string
Dynamic: ✔️
Required: ❌

`options`

Type: object
SubType: string
Dynamic: ❌
Required: ❌

Driver-specific options, specified as key/value pairs.

These options are passed directly to the driver.

Was this page helpful?

​Dbt​C​L​I

DbtCLI

enabled

exclude

include

cpus

type

kernelMemory

memory

memoryReservation

memorySwap

memorySwappiness

oomKillDisable

key

namespace

image

config

cpu

credentials

deviceRequests

entryPoint

extraHosts

host

memory

networkMode

pullPolicy

shmSize

user

volumes

auth

identityToken

password

registry

registryToken

username

capabilities

count

deviceIds

driver

options

DbtCLI

`enabled`

`exclude`

`include`

`cpus`

`type`

`kernelMemory`

`memory`

`memoryReservation`

`memorySwap`

`memorySwappiness`

`oomKillDisable`

`key`

`namespace`

`image`

`config`

`cpu`

`credentials`

`deviceRequests`

`entryPoint`

`extraHosts`

`host`

`memory`

`networkMode`

`pullPolicy`

`shmSize`

`user`

`volumes`

`auth`

`identityToken`

`password`

`registry`

`registryToken`

`username`

`capabilities`

`count`

`deviceIds`

`driver`

`options`