[jira] [Commented] (OOZIE-2877) Oozie Git Action

["Peter Bacsko (JIRA)" <ji...@apache.org>]

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

Peter Bacsko commented on OOZIE-2877:
-------------------------------------

+1 for the latest patch. 

 

I think in the current state it can be committed to master.

> Oozie Git Action
> ----------------
>
>                 Key: OOZIE-2877
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2877
>             Project: Oozie
>          Issue Type: Sub-task
>          Components: action
>    Affects Versions: 5.0.0
>            Reporter: Clay B.
>            Assignee: Clay B.
>            Priority: Major
>              Labels: action
>             Fix For: 5.1.0
>
>         Attachments: 0001-OOZIE-2877-Oozie-Git-Action.patch, 0002-OOZIE-2877-Oozie-Git-Action.patch, 0003-OOZIE-2877-Oozie-Git-Action.patch, 0004-OOZIE-2877-Oozie-Git-Action.patch, 0005-OOZIE-2877-Oozie-Git-Action.patch, 0006-OOZIE-2877-Oozie-Git-Action.patch, 0007-OOZIE-2877-Oozie-Git-Action.patch, 0008-OOZIE-2877-Oozie-Git-Action.patch, 0009-OOZIE-2877-Oozie-Git-Action.patch, OOZIE-2877.010.patch, OOZIE-2877.011.patch, OOZIE-2877.012.patch, OOZIE-2877.013-1.patch, OOZIE-2877.013.patch, OOZIE-2877.014-1.patch, OOZIE-2877.014-2.patch, OOZIE-2877.014-3.patch, OOZIE-2877.015.patch, OOZIE-2877.016.patch, OOZIE-2877.017.patch
>
>
> To aide in deploying ASCII artifacts to clusters, let's provide a tie-in for a source-code management system. Git would be my preferred choice.
> Ideally, this could handle a user's key material e.g. for an ssh key to pull down from a secured repository. This would free users from handling their own key staging and clean-up on YARN nodes and only require them to store the key secured in HDFS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)