-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CT-2066] Handle old param/flag names in new CLI #6903
Comments
After speaking with @iknox-fa, we can keep the |
@stu-k The I see it's actually missing from the class here! That's an oversight, and speaks to the way that the definition and initialization of these configs have been poorly coordinated to date. Not very high priority, so I'd be open to discussing kicking it out of scope — just want to make sure we're aligned on the functionality that's documented / expected. |
@jtcohen6 This work is currently turning out large enough that I'd rather keep that out of scope for now. |
We're renaming some flags to match the common naming convention:
no_print
→print
flags.DEFER_MODE
/ (env var)DBT_DEFER_TO_STATE
→defer
flags.FAVOR_STATE_MODE
→favor_state
flags.ARTIFACT_STATE_PATH
/ (env var)DBT_ARTIFACT_STATE_PATH
→state
--single-threaded
was renamed, but it's not something we publicly document, and it might only be relevant fordbt-rpc
?)Acceptance criteria: We continue to respect the old name:
I'm less concerned about the CLI flag, which raises a clear error already:
The text was updated successfully, but these errors were encountered: