PEX not found resources

[allcupsnotinprivate]

I have a service with the following structure:

service/
├── src/
│   ├── app/
│   │   ├── data/
│   │   │   └── config.json
│   │   ├── __init__.py
│   │   └── main.py
└── BUILD

Contents of the BUILD file:

# ===============================
# Sources and Requirements
# ===============================

python_sources(
    name="service",
    sources=["**/*.py"],
    dependencies=[
        ":service-reqs"
    ]
)

python_requirements(
    name="service-reqs"
)

files(
    name="service-files",
    sources=["**/config.json"]
)

# ===============================
# Binary Definitions
# ===============================

pex_binary(
    name="service-bin",
    output_path="service/package/bin.pex",
    execution_mode="venv",
    entry_point="app.main",
    environment=parametrize("macos", "linux"),
    layout="packed",
    dependencies=[
        ":service",
        ":service-files"
    ]
)

The problem is that the resulting .pex file does not contain any resources (specifically "data/config.json"). Why does this happen?

[jsirois]

Change files to resources: https://www.pantsbuild.org/stable/reference/targets/resources

This is an incredibly common pitfall that apparently still exists in Pants many years later and, from what I can tell, is still not documented in the likely places. For example, here: https://www.pantsbuild.org/stable/docs/python/overview/pex. Better, the command line invocation of pants package ... would warn at least when packaging a pex_binary that depended on file targets instead of silently just not including them.

You can see a working example of including resources here: https://github.com/pantsbuild/example-python/tree/main/helloworld/greet

[cburroughs]

On the how Pants handles this tangent:. I get:

21:09:51.43 [WARN] The target foo/bar/server:bin (`pex_binary`) transitively depends on the below `files` targets, but Pants will not include them in the built package. Filesystem APIs like `open()` may be not able to load files within the binary itself; instead, they read from the current working directory.
Instead, use `resources` targets. See https://www.pantsbuild.org/resources.

@allcupsnotinprivate Do you see that as well? I'm not trying to claim the WARN was sufficient or the best we can do, but wanted to start by making sure we are seeing the same thing.

[allcupsnotinprivate]

Yes, sorry, my mistake is that I defined the files as targets, not as resources. I encountered troubleshooting and saw that it is necessary to use exactly the resources. Actually, question was invented because replacing files on resources does not help, they are not initialized in .pex.

Previously used the same approach with same files, and everything worked (paths were same). Cleared cache - did not help