GitHub user vanzin opened a pull request: https://github.com/apache/spark/pull/18293
[SPARK-20379][core] Allow SSL config to reference env variables. This change exposes the internal code path in SparkConf that allows configs to be read with variable substitution applied, and uses that new method in SSLOptions so that SSL configs can reference other variables, and more importantly, environment variables, providing a secure way to provide passwords to Spark when using SSL. The approach is a little bit hacky, but is the smallest change possible. Otherwise, the concept of "namespaced configs" would have to be added to the config system, which would create a lot of noise for not much gain at this point. Tested with added unit tests, and on a real cluster with SSL enabled. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vanzin/spark SPARK-20379 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/18293.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #18293 ---- commit dc94c4b9915bb9bef24a0200f5e2475221bbf656 Author: Marcelo Vanzin <van...@cloudera.com> Date: 2017-06-12T22:26:11Z [SPARK-20379][core] Allow SSL config to reference env variables. This change exposes the internal code path in SparkConf that allows configs to be read with variable substitution applied, and uses that new method in SSLOptions so that SSL configs can reference other variables, and more importantly, environment variables, providing a secure way to provide passwords to Spark when using SSL. The approach is a little bit hacky, but is the smallest change possible. Otherwise, the concept of "namespaced configs" would have to be added to the config system, which would create a lot of noise for not much gain at this point. Tested with added unit tests, and on a real cluster with SSL enabled. ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org