Is there a way to list/filter all targets that would be used by a goal? For example, I want to know what would happen if I ran

pants package ::

-- there are many package-able target types and I don't know them all ahead of time

There's kinda an inverse of this functionality, which tells you some of the goals that can be run on a target using pants peek

% pants peek ::
...
{
    "address": "pants-plugins/experimental/swift/util_rules/compile.py",
...
    "goals": [
      "run"
    ],

Now, I could have sworn I wrote this while seeing the functionality you asked for. Specifically dealing with the

filter

https://www.pantsbuild.org/2.21/docs/using-pants/advanced-target-selection#filter-options

oh yeah, I suppose that'll work. (I could even

sed

out that part of the output, which will depend on the backends enabled in my pantsverse)

Can you describe what the call you're looking for woudl look like, with what output? Just trying to make sure I understand your question

well I'm trying to troubleshoot why my

pants package ::

is failing in github actions CI (I suspect OOM), so I wanted to get a list of what all it's trying to do and see if I can pare that down to a smaller but useful set of targets

👍 I want to say that what you're suggesting should/must be possible first-party somehow - but it's been a long time since I've needed to do similar If not, we should probably have some sort of

--filter-goal

hook, as that seems pretty useful

helpful (lucky?) that bare

pants package

prints out the command I'm looking for. But only once? if I re-run

pants package

it no longer prints the warning

Yeah, this is exactly the functionality I ran into - and I thought we had some way to trigger it

the FieldSet stuff looks like it would be an easy plugin to write

For posterity, maybe something like this?

pants peek :: | jq  '.[] | select(.goals | index("package")) | .address'

oss/pants-plugins % pants peek :: | jq  '.[] | select(.goals | index("package")) | .address' 
"examples/python/core:core-dist"
"examples/python/hellofastapi:hellofastapi-pex"
"examples/python/hellofastapi:hellofastapi-scie"
"examples/python/hellofib:hellofib-dist"
"examples/python/hellofib:hellofib-mypyc"
"examples/python/hellofib:hellofib-pex"
"examples/python/hellofib:hellofib-scie"
"examples/python/hellokivy:hellokivy-pex"
"examples/python/hellokivy:hellokivy-scie"
"examples/python/hellonumpy:hellonumpy-pex"
"examples/python/hellonumpy:hellonumpy-scie"
"examples/python/hellotyper:hellotyper-pex"
"examples/python/hellotyper:hellotyper-scie"
"examples/python/hellowebview:hellowebview-pex"
"examples/python/hellowebview:hellowebview-scie"
"examples/python/helloworld:helloworld-pex"
"examples/python/helloworld:helloworld-scie"
"pants-plugins/experimental/scie:scie-dist"

that doesn't seem to get all of them for me. e.g. my docker_image targets don't specify goals

Oh, well, that's interesting - might be a bug in the implementation

I ran into the same use case and solved it with a CLI alias of

—-publishable

, mapped to a hardcoded list of our publishable types, which are limited. We also had to add a

skip-publish

tag to that alias - to exclude some intermediate docker images that we don’t ever want to publish. There’s a skip publish param on the

docker_image

, which prevents publish but didn’t affect the alias. We then effectively use

pants list —publishable

, as a

pants package

preview in CI

I do think that, if we don't have this functionality somewhere (I could have sworn we did), it should be first-party functionality. Seems natural to have somewhere

Agree, it feels like a gap. Being able to filter on specific target types is great (nit: are these really "goal" types, not "target" types?). The same way we can say

pants test ::

makes it surprising not to be able to query "what are all the

test

-able targets"

Agreed, and year, goal oriented is how I think about this and how we use it

Would you mind writing an issue that captures that?