Parity for source freshness task/command

Describe the feature

dbt source snapshot-freshness is quite limited and a bit verbose relative to other dbt task-commands.

1. Source freshness should support full node selection syntax, including things like:

   • --select tag:something (#2369)
   • --exclude and --selector (#2729)
   • --select +downstream_resource, i.e. check freshness of all sources upstream of downstream_resource. I think this would be especially compelling for exposures!

2. Should this be renamed to avoid confusion with dbt snapshot? I think yes, and it could be as simple as calling it dbt source freshness instead—although that’s not a verb! Open to suggestions.

We’d obviously do the renaming in a way that’s backwards-compatible. Ideally, we’d rename and add functionality in the same release.

Describe alternatives you’ve considered

Leaving dbt source snapshot-freshness as is: clunky to type, wonky to use

Additional context

Is this feature database-specific? Which database(s) is/are relevant? Please include any other relevant context here.

Who will this benefit?

All current and potential users of source freshness, which is a relatively underused + under-appreciated feature! Maybe in part because it feels a bit clunky 😃

[jtcohen6]

@Kiollpt Yes, that should work now! Have you given it a try with a recent version of dbt (v0.21+)?

[jtcohen6]

1. I’m leaning dbt source freshness. I realize it’s a noun, not a verb (which other commands are), but I don’t think that’s so bad. The colloquial expression/documentation can refer to this as “checking source freshness.”
2. Yes!