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/09/17 17:24:01 UTC

[jira] [Commented] (BEAM-12734) Autopopulate Dataflow PipelineOptions from flags

    [ https://issues.apache.org/jira/browse/BEAM-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416822#comment-17416822 ] 

Beam JIRA Bot commented on BEAM-12734:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> Autopopulate Dataflow PipelineOptions from flags
> ------------------------------------------------
>
>                 Key: BEAM-12734
>                 URL: https://issues.apache.org/jira/browse/BEAM-12734
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go
>            Reporter: Robert Burke
>            Assignee: Robert Burke
>            Priority: P2
>              Labels: stale-assigned
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Go has a standard flag library which we can use to inspect all defined flags for a Dataflow job.
> We can use the set flag visitor to include them all as pipeline options when set. This allows automatic population of run specific information to the Dataflow job.
> We need to also provide a way to filter out anything Dataflow would always mention/provide anyway, to avoid cluttering the UI. Further some user defined flags may be sensitive API keys or similar, so we should provide a way for users to exclude flags from appearing in the Dataflow pipeline options.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)