-
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 deprecation warnings for renamed commands #3565
Comments
I agree! Let's do both: continue support *At least until dbt v2.0, if not longer :) |
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days. |
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days. |
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers. |
Describe the feature
In #3554, we renamed
source snapshot-freshness
->source freshness
. Both commands are supported and no deprecation warning is showed. It would be ideal to show deprecation warnings when using the old command.Describe alternatives you've considered
Support renamed commands forever via an alias and don't display any deprecation warnings. I'm perfectly happy with this answer as well, I'd happily close this issue if that is acceptable.
The text was updated successfully, but these errors were encountered: