[ https://issues.apache.org/jira/browse/OOZIE-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16445383#comment-16445383 ]
Clay B. commented on OOZIE-2877: -------------------------------- [~andras.piros] I still do not have a full cluster to try this on for finishing the documentation callouts marked with {{XXX TODO XXX}} these can be removed but these came from seeing what looked relevant from other actions. I can leave the patch as is for now blocking on me getting an Oozie 5 cluster, leave the documentation for someone with an Oozie 5 cluster handy or I can remove the documentation I do not have answers for; which would you prefer? If you have any code comments we can use the [GitHub PR|https://github.com/apache/oozie/pull/37] otherwise. > 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 > > > 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)