narrow-vegetable-37489
05/05/2023, 11:18 AMresource like behaviour --> 🧵narrow-vegetable-37489
05/05/2023, 11:19 AMresource because our Python APIs use them for request and response validation, and thus we want them to be bundled in the PEX. The “problem” is that if my Python code has a dependency on the OpenAPI target(s), those files don’t seem to become part of the PEX itself.
So, the question is...
How do I get those targets to behave more like resource? Ideally I would just add that my python_source depends on the openapi_document and then the dependency inference would make sure that my PEX contains the openapi_document as well as all relevant openapi_sources.
But...
Do I really want those tragets to behave more like resource? I mean, I do obviously, but I imagine it’s maybe not something everyone that’s using the OpenAPI backend wants? I could in my repository have both openapi_source and resource targets, but then I’d have to manage dependencies between resource and openapi_source manually - missing out on that sweet dependency inference I get if my Python code depends on the openapi_document directly.
Or... maybe I’m missing something? Help! 🙈broad-processor-92400
05/06/2023, 12:29 AMshell_command or adhoc_tool etc, where the file vs resource distinction doesn’t matter so much, I thinknarrow-vegetable-37489
05/08/2023, 2:20 PMbroad-processor-92400
05/08/2023, 9:31 PMresource is implemented...)