feat(dbt): enforce all-or-nothing opt-in for asset checks

[rexledesma]

Summary & Motivation

As the title.

How I Tested These Changes

pytest

[rexledesma]

Current dependencies on/for this PR:

• master
  • PR feat(dbt): enforce all-or-nothing opt-in for asset checks #16852 👈
    • PR feat(dbt): implement subsetting to execute dbt tests #16801

This comment was auto-generated by Graphite.

[sryza]

If this is a global setting, might it make sense as an argument to dbt_assets or somehow on the DagsterDbtTranslator, instead as test-level config?

[rexledesma]

If this is a global setting, might it make sense as an argument to dbt_assets or somehow on the DagsterDbtTranslator, instead as test-level config?

We could probably consider adding it to DagsterDbtTranslator, since that's already threaded through the system. That should probably go into its own change though.

[sryza]

We could probably consider adding it to DagsterDbtTranslator, since that's already threaded through the system. That should probably go into its own change though.

With that change, would we also need this change?

[rexledesma]

Unless we want to break users who have been enabling asset checks using their dbt project's metadata, we will still need this change.

[sryza]

Unless we want to break users who have been enabling asset checks using their dbt project's metadata, we will still need this change.

I think we should be comfortable breaking them if we think it's the right direction. We expect users who sign up to be design partners for features before their public release to be able to sustain breaking changes to those features.