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 2020/08/07 17:07:01 UTC
[jira] [Commented] (BEAM-7519) Improve work with SSL/TLS
certificates in SDK IO, for Google Dataflow
[ https://issues.apache.org/jira/browse/BEAM-7519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173311#comment-17173311 ]
Beam JIRA Bot commented on BEAM-7519:
-------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.
> Improve work with SSL/TLS certificates in SDK IO, for Google Dataflow
> ---------------------------------------------------------------------
>
> Key: BEAM-7519
> URL: https://issues.apache.org/jira/browse/BEAM-7519
> Project: Beam
> Issue Type: Wish
> Components: io-ideas, io-java-elasticsearch, io-java-gcp, io-java-kafka
> Reporter: Oleksandr Priadko
> Priority: P3
>
> Sinks like Kafka or Elasticsearch have worked with SSL/TLS. But all of these can read only certificates from a local machine (use java.io.File#File(java.lang.String).
> In the case of Google Dataflow, we can not easily copy files to a worker, I see two possible variants to read certificates from the worker:
> 1) somehow copy certificates to a worker from GC Storage
> 2) in Kafka IO or Elasticsearch IO read certificates directly from GC Storage
> Any thoughts about how I can solve this issue easily or mb other variants will be helpful.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)