Github user budde commented on the issue:
https://github.com/apache/spark/pull/16744
@brkyvz I share your concerns around expanding this API further than
necessary. I think I'm okay with this as long as we're fairly confident the
builder pattern work can be merged in the same Spark release. My reluctance
here is that forcing users who want to use STS to provide static credentials
for the long-lived auth to STS itself will be a security regression for folks
using EC2 where [IAM instance
profiles](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html)
provide a secure way of avoiding potential problems with static credential
management.
As you've pointed out though, this is less of a concern if we can deprecate
the brittle ```KinesisUtils.createStream()``` API with a flexible builder class.
I'll give another look over the ```createStream()``` implementations you're
suggesting we remove and push an update to this PR if I don't have any
objections.
---
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
