For the Kubernetes work, we’re planning on changin...
# contributing-to-airbyte
j
For the Kubernetes work, we’re planning on changing the internal usage of
ProcessBuilderFactory
to something that returns a
Process
instead of a
ProcessBuilder
, so more of a
ProcessFactory
. This is because we don’t to allow the various
ProcessBuilder
modifications that aren’t supported across both Docker and Kubernetes. This implementation is just a minor class refactor. Just wanted to get a gut check if anyone feels like this is a terrible idea.