You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexander Rojas (JIRA)" <ji...@apache.org> on 2015/01/14 18:13:34 UTC

[jira] [Comment Edited] (MESOS-1498) Expose ACLs on an endpoint

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

Alexander Rojas edited comment on MESOS-1498 at 1/14/15 5:12 PM:
-----------------------------------------------------------------

As I see it, I can see the contents of the acls via the {{/state.json}} endpoint whether it is passed as a file or as a string or a file. 

Vinod Kone: Can you confirm if the issue is still open or if there's anything else to be done here?


was (Author: arojas):
As I see it, I can see the contents of the acls via the {{/state.json}} endpoint whether it is passed as a file or as a string or a file. Can you confirm if the issue is still open or if there's anything else to be done here?

> Expose ACLs on an endpoint
> --------------------------
>
>                 Key: MESOS-1498
>                 URL: https://issues.apache.org/jira/browse/MESOS-1498
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Vinod Kone
>            Priority: Minor
>
> Currently, if "--acls" are specified via JSON it is exposed via /state.json. But if "--acls" is a file path, there is no easy way to see the ACLs. It would be nice if the Authorizer has its own endpoint to show this information.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)