Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1120#issuecomment-55552288
From a security perspective I think once concern is the following. Say a
company is in a workflow where user A launches clusters (e.g. an ops person)
and user B, C, D use the Spark clusters with supplied login credentials. With
this patch, now we'll copy user A's AWS credentials into a file on the cluster
that user B, C, D, etc can read. And this change will basically be silently
introduced. Am I correct in this understanding?
That's IMO too big of a change to introduce silently. But maybe we can
guard this with a flag. I do agree this is a super useful feature to have.
Jenkins, test this please.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
