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/03/25 17:19:00 UTC
[jira] [Commented] (BEAM-11680) custom container credentials
[ https://issues.apache.org/jira/browse/BEAM-11680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308836#comment-17308836 ]
Beam JIRA Bot commented on BEAM-11680:
--------------------------------------
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.
> custom container credentials
> ----------------------------
>
> Key: BEAM-11680
> URL: https://issues.apache.org/jira/browse/BEAM-11680
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Affects Versions: 2.27.0
> Reporter: Travis Webb
> Priority: P2
> Labels: stale-P2
>
> I did not find a Jira ticket for this TODO, so I wanted to create one: [https://github.com/apache/beam/blob/master/sdks/python/apache_beam/runners/portability/fn_api_runner/worker_handlers.py#L757]
>
> This seems to affect PortableRunner. Without the ability to pass credentials to a container at runtime, e.g. GOOGLE_APPLICATION_CREDENTIALS, the credentials must be built into the container at build-time, which is not ideal (nor is this limitation documented, as far as I can tell)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)