-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
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
Add a command line flag to enable or disable color output #2192
Comments
Thanks for the report @Matt343! I think we'll have a good answer on boolean env vars for 0.17.0, but I'm not opposed to |
hey @invinceyble - I think c38c8d5 is a great source of inspiration for this flag :) |
@invinceyble Are you working on this? If not, I can pick this up this week |
@rsenseman Totally slipped off my radar, all yours! :) |
Describe the feature
The use_colors config option enables or disables console escape codes in the DBT command output, but you cannot currently override the value from
profiles.yml
when running a command. Adding--use-colors
and--no-use-colors
(similar to how partial parsing is handled) would allow us to be explicit with what output format we need in each environment without needing completely separateprofiles.yml
files.Describe alternatives you've considered
We handle other environment specific values in
profiles.yml
usingenv_var
Jinja blocks, but the boolean options in theconfig
section do not seem to support that mechanism.Additional context
Who will this benefit?
DBT command line users who want to configure color output differently for different commands/contexts, or who want color output usually but occasionally pipe the output of DBT into other tools.
The text was updated successfully, but these errors were encountered: