[
https://issues.apache.org/jira/browse/BEAM-7519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164541#comment-17164541
]
Beam JIRA Bot commented on BEAM-7519:
-------------------------------------
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.
> 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: P2
> Labels: stale-P2
>
> 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)
