beam-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (BEAM-10671) Add environment configuration fields as first-class pipeline options
Date Tue, 29 Sep 2020 23:12:00 GMT


ASF GitHub Bot logged work on BEAM-10671:

                Author: ASF GitHub Bot
            Created on: 29/Sep/20 23:11
            Start Date: 29/Sep/20 23:11
    Worklog Time Spent: 10m 
      Work Description: ibzib commented on pull request #12576:

   Python precommit failures seem to be unrelated: BEAM-10985
   I won't merge until it passes, since it seems the cause of failure is that no unit tests
are running.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 492712)
    Time Spent: 10h 10m  (was: 10h)

> Add environment configuration fields as first-class pipeline options
> --------------------------------------------------------------------
>                 Key: BEAM-10671
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-harness
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: P2
>          Time Spent: 10h 10m
>  Remaining Estimate: 0h
> The pipeline option --environment_config has completely different usages depending on
the value of --environment_type. This is confusing for the user and hard to check. Additionally,
--environment_config is a JSON blob for --environment_type=PROCESS. This JSON blob is a pain
to escape and pass around compared to a collection of flat strings.
> We should replace --environment_config with first-class / top-level pipeline options
for each environment type:
> --environment_container_image
> --environment_os
> --environment_architecture
> --environment_variables
> --environment_service_address
> (none)
> This way we can validate that the user is configuring these options correctly (ie give
a warning or error if they use options that do not apply to their chosen --environment_type).
> We can deprecate the --environment_config option, logging a warning until removing this
option altogether in a future Beam release.
> []

This message was sent by Atlassian Jira

View raw message