[ 
https://issues.apache.org/jira/browse/TWILL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948658#comment-15948658
 ] 

ASF GitHub Bot commented on TWILL-189:
--------------------------------------

GitHub user chtyim opened a pull request:

    https://github.com/apache/twill/pull/48

    (TWILL-189) Allows secure store update with different UGI

    - Deprecated the old TwillRunner.scheduleSecureStoreUpdate
    - Added new TwillRunner.setSecureStoreRenewer method
      - Takes SecureStoreRenewer that writes SecureStore via
      SecureStoreWriter
        - The renewer implementation can use appropriate UGI.doAs to make
        call to SecureStoreWriter

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/chtyim/twill feature/TWILL-189

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/twill/pull/48.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 #48
    
----
commit 292008e903866b828e32d5a93aa2a7b6775e46c7
Author: Terence Yim <cht...@apache.org>
Date:   2017-03-28T21:31:06Z

    (TWILL-189) Allows secure store update with different UGI
    
    - Deprecated the old TwillRunner.scheduleSecureStoreUpdate
    - Added new TwillRunner.setSecureStoreRenewer method
      - Takes SecureStoreRenewer that writes SecureStore via
      SecureStoreWriter
        - The renewer implementation can use appropriate UGI.doAs to make
        call to SecureStoreWriter

----


> SecureStoreUpdater should support updating secure store as other users
> ----------------------------------------------------------------------
>
>                 Key: TWILL-189
>                 URL: https://issues.apache.org/jira/browse/TWILL-189
>             Project: Apache Twill
>          Issue Type: New Feature
>          Components: api
>    Affects Versions: 0.7.0-incubating
>            Reporter: Ali Anwar
>             Fix For: 0.11.0
>
>
> SecureStoreUpdater always creates secure stores for the current user and 
> writes these as the current user.
> It should allow writing the secure store as a different user.
> For an example use case, see: https://github.com/caskdata/cdap/pull/6380



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to