feat(cli): Materialization selectors - #52
Merged
Merged
Conversation
CasperTeirlinck
changed the title
CasperTeirlinck
marked this pull request as ready for review
July 14, 2026 12:35
jvanbuel
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sometimes, you want to only materialize/show a subset of the metrics (by default) when running
checkup run.For example you define metrics in your config, where a subset of them are aggregates/derivatives of those other metrics which then provide the most valuable feedback/scoring for a data product (commonly called
healthchecks). But you still need to include the underlying metrics in your config. If you provide a config with e.g. the console materializer, you only want to see the healthchecks.Or it can just be useful for ad-hoc usage of the checkup CLI.
To support this, this PR adds a dbt-style selector mechanism so you can explicitly only include those metrics that make sense to represent in the chosen materialization:
Examples:
checkup run --select "healthcheck_*"checkup run --select "tag:healthcheck"checkup run --select "type:dbt_tests"In the config you can also set a default select argument:
Note: the tags field on a Metric were not yet implemented, so this PR also adds that.