[Bug] [Spike] indirect_selection in yaml selector definition doesn't work about dbt-core HOT 4 CLOSED

We do that kind of resolution in the flags.py file, so I guess this is similar to that.

from dbt-core.

We should write some brief docs about how selector works in general and have that added to the repo as a read me

from dbt-core.

@gshank What I found is that the indirect selection in selectors.yml works, but you cannot overwrite it with args passed in from CLI.

So for this jaffle shop model orders, I defined a selectors.yml looking like this

selectors:
  - name: nodes_to_joy
    definition:
      union:
        - method: path
          value: models/marts/orders.sql
          children: false
          parents: false
          indirect_selection: buildable

And by changing the indirect_selection value and run dbt ls --selector nodes_to_joy, I found that the number of things being selected goes from 3 to 4, which means it works.
But if I try to run dbt ls --selector nodes_to_joy --indirect-selection eager with buildable as a value inside, I see effect of buildable indirect selection.
If I do not specify indirect-selection in the yaml selectors file, I see the effect of eager and can't overwrite it with CLI args.

This doesn't match this PR description but matches what Doug said in his issue. Thouths? Any issue with the way I test?

from dbt-core.

I did find out the reason for the behavior Doug mentioned is that the rendered.selectors_dict here does not contain a resolved dict that has default value inside.

@gshank do you know in other places how do we resolve these kind of stuff? I think we should probably setup a patten to do resolution(CLI, env var, project file definition).

from dbt-core.