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
capture dbt cli submitted command in run_results.json, this is to help with logging/auditing, where we need some way to identify various runs.
no proper alternative, all the workarounds are fragile and short living at best, examples:
cross databases feature.
hopefully all dbt users, but main audience is dbt users trying to audit/investigate/optimize their runs
The text was updated successfully, but these errors were encountered:
I'm super supportive of this feature - thanks for opening it @younescha! I added this to the milestone for our next release, dev/marian-anderson.
dev/marian-anderson
Sorry, something went wrong.
gshank
Successfully merging a pull request may close this issue.
Describe the feature
capture dbt cli submitted command in run_results.json,
this is to help with logging/auditing, where we need some way to identify various runs.
Describe alternatives you've considered
no proper alternative, all the workarounds are fragile and short living at best, examples:
Additional context
cross databases feature.
Who will this benefit?
hopefully all dbt users, but main audience is dbt users trying to audit/investigate/optimize their runs
The text was updated successfully, but these errors were encountered: