-
Notifications
You must be signed in to change notification settings - Fork 950
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
All CLI flags should be passed after subcommand #4041
Labels
cloud-cli-beta
content
Improvements or additions to content
improvement
Use this when an area of the docs needs improvement as it's currently unclear
Comments
jtcohen6
added
content
Improvements or additions to content
improvement
Use this when an area of the docs needs improvement as it's currently unclear
blocked_by_dev
Awaiting merge of PR with associated functionality
labels
Sep 7, 2023
4 tasks
@jtcohen6 , confirming this is no longer blocked by dev, right? |
jtcohen6
removed
the
blocked_by_dev
Awaiting merge of PR with associated functionality
label
Sep 28, 2023
@mirnawong1 Correct! Thanks for being on top of it :) Most of this has been updated in
|
This was referenced Oct 3, 2023
Closed
mirnawong1
added a commit
that referenced
this issue
Oct 17, 2023
<p><a href="https://www.notion.so/dbtlabs/Prod-Docs-Beta-Cloud-CLI-Oct-9th-a389341b7c1f45e2b7c162e4de591d90?d=2b3208f1ff8c49698fde7b3946b86e91">Docs project</a></p> this branch and PR addresses docs changes for the cloud-cli beta and SL GA launch Closes #4041 #4014 #4040
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
cloud-cli-beta
content
Improvements or additions to content
improvement
Use this when an area of the docs needs improvement as it's currently unclear
Docs project
Contributions
Link to the page on docs.getdbt.com requiring updates
https://docs.getdbt.com/reference/global-configs/command-line-flags
What part(s) of the page would you like to see updated?
For better consistency, all flags should be passed after the subcommand.
This includes "global" flags (supported for all commands) that have historically been passed before the subcommand:
We could continue supporting the latter for backward compatibility, but make clear that it is legacy/deprecated functionality and liable to be removed in the future. It is not supported to pass the same flag before "before" and "after."
This should be much easier for everyone, as it doesn't require remembering which flags are "global" or "not global," and which ones are supported in both places for legacy reasons.
Additional information
Blocked by:
The text was updated successfully, but these errors were encountered: