Details
-
Bug
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
Description
This causes a problem if something depends on the harness but does not want the harness's copy of its dependencies. I know we intend to break the dependency on the Dataflow runner. It also bundles a couple other things unshaded.
Mostly, the harness should be executed entirely containerized so it doesn't matter, in which case there's no need to relocate anything, and bundling is just a convenience. But we should have a clear policy that we adhere to. Either it is a library and should have good hygeine, or if it doesn't have good hygeine it must not be used as a library.
Attachments
Issue Links
- links to