Support model selection based on materialization type

[azhard]

Describe the feature

Current model selection syntax works with selecting based on model names, sources, tags, packages, and paths. These solve the majority of potential use cases but adding the ability to select models based on a materialization type would be very handy.

A specific example where that can be used: my team's dbt setup currently auto-runs changed models on production when an MR gets merged to master, however we realistically only want to deploy changed views and not to cause incremental materializations for example as those are typically based on a schedule.

I imagine as an actual CLI command this would look something like when implemented:

dbt run --models materialization:view

Describe alternatives you've considered

This same behaviour can be achieved if a user tags all view (or non-view) models but this is more cumbersome so not ideal.

Additional context

This feature should be supported across databases.

Who will this benefit?

Any dbt user who wants to trigger runs based on a materialization type.

[drewbanin]

hey @azhard - thanks for opening this issue. This is a dupe of #2425, prioritized for our next feature release. Closing this!

[azhard]

Awesome! Thanks @drewbanin