My req changes is solely because I'm curious about what your vision for the future of PipelineReference is? Does it exist in the long-temr/
No, but I was getting kind of difficult merges, so it actually got rebased into https://dagster.phacility.com/D3118
did you miss a commit in your rebase? i don't see get_legacy_pipeline_selector added in utils.py (there are no changes to utils)
fix tests, update, rebase
hmm definitely not crazy - will need to think on this one a bit
- instead of making it an extra arg, we use the existing solid_subset: execute_pipeline(pipeline, solid_subset=['*some_solid', 'other_solid_a', 'other_solid_b+'])
- more tests to cover multiple clauses (disjoint, overlapping) and invalid queries
- get_solid_subset_from_query(pipeline_def, query) where query is str => parse_solid_subset(pipeline_def, solid_subset) where solid_subset is List[str]
- more tests to cover multiple clauses, invalid syntax, and duplication
fine place to start - some edges to polish as we use it a bit and understand the ergonomics better
how bout just PipelineSnapshotLineage?
Seems like this name should indicate that it is a legacy/single-env-single-repo codepath
Just req'ing changes so we can get the docs in there that @prha mentioned because I think that's a good call.