Hi all, We're using the orchestrator dagster and are interested in using pants to bring everything in to a mono-repo. Dagster has an idea of "branch deployments", where you can create an ephemeral environment which contains the Dag in your pull request so you can try it out before merging to main. I'm wondering if there is some sort of control logic that would allow me to say "use pants to create docker images for any projects which are impacted by these changes", followed by "trigger the branch deployment logic for each repo which now has a new docker image". In other words, if I had 10 projects, but the changes I made only actually led to two of my repos requiring redeployment, I'd only want to do deployments for impacted repos

using something along the lines of

pants --changed-since=main --changed-dependents=transitive publish --output=result.json ::

and inspecting the

result.json

to trigger the deployment step should get you close. Adapt the

::

accordingly to select the set of (docker) targets you want to work with. https://www.pantsbuild.org/2.19/reference/goals/publish#output

Sounds great, thanks!