We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue is not a blocker but sth worth investigating long term.
As long as you add outputFiles property to the dbtCLI task, the models are no longer rendered. We should investigate why
Reproducer:
setup flow:
id: upload_dbt_project namespace: company.datateam.dbt tasks: - id: wdir type: io.kestra.plugin.core.flow.WorkingDirectory tasks: - id: git_clone type: io.kestra.plugin.git.Clone url: https://github.com/kestra-io/dbt-example branch: master - id: upload type: io.kestra.plugin.core.namespace.UploadFiles namespace: "{{ flow.namespace }}" files: - "glob:**/dbt/**"
then:
id: dbt_build namespace: company.datateam.dbt tasks: - id: dbt type: io.kestra.plugin.dbt.cli.DbtCLI namespaceFiles: enabled: true containerImage: ghcr.io/kestra-io/dbt-duckdb:latest projectDir: dbt commands: - dbt build --project-dir dbt --profiles-dir dbt loadManifest: key: manifest.json namespace: "{{ flow.namespace }}" storeManifest: key: manifest.json namespace: "{{ flow.namespace }}" taskRunner: type: io.kestra.plugin.scripts.runner.docker.Docker
the above flow will work fine, but then try adding:
outputFiles: - "**/*.json"
dbt outputs are no longer rendered
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue description
This issue is not a blocker but sth worth investigating long term.
As long as you add outputFiles property to the dbtCLI task, the models are no longer rendered. We should investigate why
Reproducer:
setup flow:
then:
the above flow will work fine, but then try adding:
dbt outputs are no longer rendered
The text was updated successfully, but these errors were encountered: