[ https://issues.apache.org/jira/browse/OOZIE-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458578#comment-16458578 ]
Andras Piros commented on OOZIE-2877: ------------------------------------- [~clayb] here we go w/ [*the updated patch*|https://issues.apache.org/jira/secure/attachment/12921251/OOZIE-2877.010.patch]. Can you please upload to your [*ReviewBoard review request*|https://reviews.apache.org/r/59620/]? Thanks! Changes: * slight refactor * all test cases are running by default * an example workflow w/ a simple Git action is provided * tested on {{5.1.0-SNAPSHOT}} [~gezapeti] could you please also review? Thanks! > 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. > Assignee: Clay B. > Priority: Major > Labels: action > Fix For: trunk > > 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 > > > 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)