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
I'm trying to setup a VSCode dev container with dbt and dbt-bash-completion But I can't get it working.
dbt
dbt-bash-completion
You can reproduce it by running: docker run -it --rm python:3.13-slim bash
docker run -it --rm python:3.13-slim bash
And inside the docker container:
apt update apt install curl pip install dbt-core curl https://raw.githubusercontent.com/fishtown-analytics/dbt-completion.bash/master/dbt-completion.bash > ~/.dbt-completion.bash source ~/.dbt-completion.bash
When double tabbing it will just do nothing.
I made sure that bash-completion works by installing:
bash-completion
apt install bash-completion -y $ dd --help --version bs= cbs= conv= count= ibs= if= iflag= obs= of= oflag= seek= skip= status=
Or am I missing something obvious?
The text was updated successfully, but these errors were encountered:
The bash completion has much less features than the zsh one. It doesn't provide parameters completion for example.
For bash, we are only adding model names, so you would need to be at the root of your folder and have the manifest.json already generated.
manifest.json
Then, you can do dbt run --select <TAB> and you should see the list of models to run.
dbt run --select <TAB>
Sorry, something went wrong.
No branches or pull requests
I'm trying to setup a VSCode dev container with
dbt
anddbt-bash-completion
But I can't get it working.You can reproduce it by running:
docker run -it --rm python:3.13-slim bash
And inside the docker container:
When double tabbing it will just do nothing.
I made sure that
bash-completion
works by installing:Or am I missing something obvious?
The text was updated successfully, but these errors were encountered: