[ 
https://issues.apache.org/jira/browse/BEAM-11780?focusedWorklogId=550843&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-550843
 ]

ASF GitHub Bot logged work on BEAM-11780:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Feb/21 18:54
            Start Date: 10/Feb/21 18:54
    Worklog Time Spent: 10m 
      Work Description: tvalentyn commented on pull request #13933:
URL: https://github.com/apache/beam/pull/13933#issuecomment-776933914


   Thanks all for the input.
   
   Can we 
   1) add instructions on how to regenerate this client somewhere in the code 
or documentation, and leave pointers on BEAM-11780? 
   2) move the generated code to apache_beam/io/gcp/internal/clients/
   3) create an (internal) issue for cloudbuild ownernes that documents the 
friction points?
   
   Thanks!
   


----------------------------------------------------------------
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:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 550843)
    Time Spent: 2h 40m  (was: 2.5h)

> Use vendor cloud build client library so that cloudbuild-python dependency 
> can be removed
> -----------------------------------------------------------------------------------------
>
>                 Key: BEAM-11780
>                 URL: https://issues.apache.org/jira/browse/BEAM-11780
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow, sdk-py-core
>            Reporter: Yichi Zhang
>            Assignee: Yichi Zhang
>            Priority: P2
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> This will make dataflow internal testing with prebuild sdk container workflow 
> much easier.



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

Reply via email to