Feature request: check-model-has-at-least-meta-keys about dbt-checkpoint HOT 2 CLOSED

I found this old issue hanging around.

The feature requested on this issue was started on #65 and then tweaked and merged on #83. Thanks, @BAntonellini and @ssassi! 🙌

from dbt-checkpoint.

I just started working on this one and I realized that the error message from check-source-has-meta-keys also gives a false impression that the check is checking for the existence of "at least" the meta keys passed as argument.

Example (from the existing test suite):

• There's a model with meta keys foo and bar
• The test is executed by running this check with --meta-keys foo
• The check fails, as the current implementation needs an exact match, and not "at least"

So far, so good. But then the error message to the user is:

aa/bb/with_meta.sql: does not have some of the meta keys defined:
- foo

Which is misleading, since the model does have foo defined.

Just writing here as a reminder to also double-check the error messages on the proposed PR.

from dbt-checkpoint.