Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Hi, It’s not very clear to me how the `complete_platforms` option should look like in `pex_binary`
The docs for <https://pex.readthedocs.io/en/latest/buildingpex.html#complete-platform|pex> says
&gt;  The complete platform can be either a path to a file containing JSON data or else a JSON object literal.
On the other hand, docs for <https://www.pantsbuild.org/docs/reference-pex_binary#codecomplete_platformscode|pex_binary> says
&gt; Complete platforms should be addresses of `file` targets that point to files that contain complete platform JSON as described by <https://pex.readthedocs.io/en/latest/buildingpex.html#complete-platform|Pex>

I think an example would be helpful like we have for  <https://www.pantsbuild.org/docs/reference-pex_binary#codeplatformscode|platforms>

Even better imo would be improving the API: <https://github.com/pantsbuild/pants/issues/15234>

Help absolutely appreciated if anyone is interested

I would be interested in making the required change. Although from the ticket it’s not very clear to me what needs to be done.

opinions on whether we should support this?

&gt; or else a JSON object literal.
It's easier if we only do file paths

I think it's alright as long as we make it clear in the docs.