Allow selectors.yml to optionally define a schedule property for a selector

[bgajdzis-forto]

Ignored by DBT but available for documentation and potential integrations. It's a significant enough bit of metadata that it deserves its own place.

[cnolanminich]

Out of curiosity, would defining it as a meta tag property not satisfy your use case? We've discussed documenting schedule in the past and the meta dictionary is the place we would do it

[bgajdzis-forto]

Maybe I'm doing something wrong, but it seems to me that meta is not an accepted property in the selectors.yml file either. If that were available, I'm sure it would work just as well as having the schedule as a top-level property.
Could you share a link to that discussion you mentioned? I couldn't find it, and I'd like to catch up on it before I start trying to reinvent the wheel here.

[cnolanminich]

the following works for me the same:

# dbt project.yml

models:
  my_project:
    my_folder:
      my_table:
        +meta:
          test_meta_flag: "my_value"

dbt ls -s +config.meta.test_meta_flag:'my_value'

# selector.yml
selectors:
  - name: find_a_meta_tag
    definition:
      union:
        - method: config.meta.test_meta_flag
          value: 'my_value'

dbt ls --selector find_a_meta_tag 

both return my_table as a result

[bgajdzis-forto]

Thanks for the suggestion! I'd say it's a little roundabout, as we'd essentially be defining the selector only by the means of tags in the project.yml file. If I already created a set of more complex selectors, using some advanced features and now I want to decorate them with a schedule, I'm in a more difficult position. This is also less readable than what the selector notation normally allows for. I imagine that this can be automated, of course, which in a big project will be the case anyway.