You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2020/02/03 21:57:41 UTC
[GitHub] [druid] zachjsh commented on issue #9305: Add support for optional
cloud (aws, gcs, etc.) credentials for s3 for ingestion
zachjsh commented on issue #9305: Add support for optional cloud (aws, gcs, etc.) credentials for s3 for ingestion
URL: https://github.com/apache/druid/issues/9305#issuecomment-581638464
Thanks for proposing this @maytasm3, I think this would be a great addition. Just to confirm, if an ingestion spec was loaded with the same accessKey and secretAccessKey as another previous ingestions spec we would keep the old client around in this case and reuse it, or would we create a new client on the fly? It sounds like we already have a mechanism in place for encrypting fields in the ingestion spec, is that right?
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org