Details
-
Improvement
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
Description
To allow runners to handle current and future SDK harnesses uniformly, each SDK harness must be packaged as a docker container image satisfying the contact proposed here:
https://s.apache.org/beam-fn-api-container-contract
The suggested structure is to use a Dockerfile with all dependencies (JRE, python 2.7, etc) and a separate minimal "boot" program in Go that retrieves staged files and invokes the SDK-specific harness. This structure allows flexibility to set up the environment dynamically as well as code sharing across SDKs.
Attachments
Issue Links
- is depended upon by
-
BEAM-2878 Release process for container images
- Open
1.
|
Add provision api proto | Resolved | Henning Rohde | |
2.
|
Python SDK harness container | Resolved | Henning Rohde | |
3.
|
Java SDK harness container | Resolved | Henning Rohde |