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

Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/09/28 19:48:00 UTC

[jira] [Commented] (GEODE-3703) rename JAR resource to DEPLOY

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

ASF subversion and git services commented on GEODE-3703:
--------------------------------------------------------

Commit ceec2c0d4f524c6353dd9a79b8867b5eb2806225 in geode's branch refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ceec2c0 ]

GEODE-3703: rename target permission from JAR to DEPLOY


> rename JAR resource to DEPLOY
> -----------------------------
>
>                 Key: GEODE-3703
>                 URL: https://issues.apache.org/jira/browse/GEODE-3703
>             Project: Geode
>          Issue Type: Sub-task
>          Components: docs, security
>            Reporter: Swapnil Bawaskar
>             Fix For: 1.3.0
>
>
> We currently have a JAR resource introduced with finer grained security (not released yet). Since the idea behind this resource is to control who has authorization to deploy jar files to the geode cluster, I think a better name for this resource would be DEPLOY.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)