You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/01/05 17:13:01 UTC
[jira] [Commented] (BEAM-10671) Add environment configuration
fields as first-class pipeline options
[ https://issues.apache.org/jira/browse/BEAM-10671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259068#comment-17259068 ]
Beam JIRA Bot commented on BEAM-10671:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> Add environment configuration fields as first-class pipeline options
> --------------------------------------------------------------------
>
> Key: BEAM-10671
> URL: https://issues.apache.org/jira/browse/BEAM-10671
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py-harness
> Reporter: Kyle Weaver
> Priority: P2
> Labels: stale-P2
> Time Spent: 11h
> 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:
> DOCKER
> --environment_container_image
> PROCESS
> --environment_os
> --environment_architecture
> --environment_variables
> EXTERNAL
> --environment_service_address
> LOOPBACK
> (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.
> [https://beam.apache.org/documentation/runtime/sdk-harness-config/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)