#18169 poetry_requirements target issue when using multiple resolves via parametrize Issue created by tareshsethi Describe the bug I'm running into an issue where I cannot peek or list the

poetry_requirements

target when using multiple resolves with parametrize. My

poetry_requirements

in

3rdparty/Build

looks like:

poetry_requirements(
    resolve=parametrize("python-default", "py39")
)

and my

pants.toml

looks like this

...
[python]
enable_resolves = true
default_resolve = 'python-default'
resolves = "{'python-default': '3rdparty/python/default.lock','py39': '3rdparty/python/py39.lock'}"
resolves_to_interpreter_constraints = "{'python-default': ['==3.10.9'],'py39': ['==3.9.10']}"
interpreter_constraints = ["==3.10.9"]
...

When I run

./pants list 3rdparty::

, i get

3rdparty@resolve=python-default
3rdparty@resolve=py39
3rdparty#Click@resolve=py39
3rdparty#Click@resolve=python-default
...

and then when i try to peek into

3rdparty@resolve=python-default

, i get

Unknown goal: 3rdparty@resolve=python-default
Use `./pants help` to get help.
Use `./pants help goals` to list goals

I think this issue is resolved if you add a name to the

poetry_requirements

Pants version 2.14.0 OS MacOS Additional info Add any other information about the problem here, such as attachments or links to gists, if relevant. pantsbuild/pants