beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-2876) Add provision api proto
Date Fri, 22 Sep 2017 18:20:00 GMT


ASF GitHub Bot commented on BEAM-2876:

GitHub user herohde opened a pull request:

    [BEAM-2876] Add preliminary provision API

    Add provisioning API for the portability container contract. The pipeline options
    match the type used in the job submission request.

You can merge this pull request into a Git repository by running:

    $ git pull containers

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3885
commit dc340577bc51ba123aa1aa62caa86882e3813561
Author: Henning Rohde <>
Date:   2017-09-22T17:41:28Z

    [BEAM-2876] Add preliminary provision API


> Add provision api proto
> -----------------------
>                 Key: BEAM-2876
>                 URL:
>             Project: Beam
>          Issue Type: Sub-task
>          Components: beam-model
>            Reporter: Henning Rohde
>            Assignee: Henning Rohde
>              Labels: portability
> As per discussion in, we need to
define the provision API to allow boot code access to pipeline options, in particular.
> It is proposed as a separate API instead of merging it with control or artifact:
>    (1) Not merging with control avoids having the boot code talk to control, only to
disconnect and have the SDK harness connect. The runner can't then use the lifetime of the
connection to be the lifetime of the SDK harness.
>    (2) Not merging with artifact allows for simple, reusable artifact proxies.

This message was sent by Atlassian JIRA

View raw message