[
https://issues.apache.org/jira/browse/BEAM-13295?focusedWorklogId=685416&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-685416
]
ASF GitHub Bot logged work on BEAM-13295:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Nov/21 16:47
Start Date: 23/Nov/21 16:47
Worklog Time Spent: 10m
Work Description: pabloem commented on pull request #16046:
URL: https://github.com/apache/beam/pull/16046#issuecomment-976837487
I guess this means that we will have a go.mod file for the playground that
we reutilize for all pipelines, right? Let's document this somewhere so that
others will understand the way the go SDK environment works?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 685416)
Time Spent: 20m (was: 10m)
> [Playground] Implement copying a prepared go mod
> ------------------------------------------------
>
> Key: BEAM-13295
> URL: https://issues.apache.org/jira/browse/BEAM-13295
> Project: Beam
> Issue Type: Bug
> Components: beam-playground
> Reporter: Pavel Avilov
> Assignee: Pavel Avilov
> Priority: P3
> Labels: beam-playground-backend, beam-playground-sprint-4
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Should add file copying functions in LifeCycle and implement coping the
> prepared go mod file for go SDK
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
