You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Clay B. (JIRA)" <ji...@apache.org> on 2017/05/03 06:44:04 UTC

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

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

Clay B. commented on OOZIE-2877:
--------------------------------

I just so happen to have an implementation of something like this and will work to get a patch up for review in the next week.

> Oozie Git Action
> ----------------
>
>                 Key: OOZIE-2877
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2877
>             Project: Oozie
>          Issue Type: Sub-task
>          Components: action
>            Reporter: Clay B.
>
> 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
(v6.3.15#6346)