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/06/26 02:23:00 UTC
[jira] [Updated] (OOZIE-2877) Oozie Git Action
[ https://issues.apache.org/jira/browse/OOZIE-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clay B. updated OOZIE-2877:
---------------------------
Attachment: 0003-OOZIE-2877-Oozie-Git-Action.patch
This has the review board comments published. Still need to write documentation and get some clarification on review board comments.
> 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.
> 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
>
>
> 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.4.14#64029)