[
https://issues.apache.org/jira/browse/OOZIE-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443409#comment-16443409
]
ASF GitHub Bot commented on OOZIE-2877:
---------------------------------------
GitHub user cbaenziger opened a pull request:
https://github.com/apache/oozie/pull/37
OOZIE-2877 Oozie Git Action
This is for code review of
[OOZIE-2877](https://issues.apache.org/jira/browse/OOZIE-2877).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cbaenziger/oozie git_action_master_Apr_18_2018
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/oozie/pull/37.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #37
----
commit 824cfb855a3d970df0d0c194266ac6a6dfe29ccf
Author: Clay Baenziger <cbaenziger@...>
Date: 2017-05-02T01:37:20Z
OOZIE-2877 Oozie Git Action
----
> 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
>
>
> 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)
