mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Bannier <>
Subject Re: Review Request 47891: Added RUN_TASK authorization action.
Date Mon, 30 May 2016 13:42:57 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated May 30, 2016, 3:42 p.m.)

Review request for mesos, Adam B, Alexander Rojas, Joerg Schad, and Michael Park.


Rebased and addressed comments by Joerg and Adam.

Bugs: MESOS-5459

Repository: mesos


Authorization requests for RUN_TASK actions can pass `SOME`
authorization object either in a `FrameworkInfo` holding a user, or a
`TaskInfo` with optionally a `CommandInfo` which can optionally hold a
user. If either of these fields is set it will be used as the object;
otherwise an `ANY` type authorization object will be created.

`RUN_TASK` aliases `RUN_TASK_WITH_USER` which becomes deprecated with

Diffs (updated)

  include/mesos/authorizer/authorizer.proto 4478bbd3c8f5c1fb862c2c6bd450689d870f7059 
  src/authorizer/local/authorizer.cpp 547bbdd6c3605eadd23d2d2717a3fd362a616de5 
  src/master/master.cpp a6f740f7f71c4b54208e923025d32e0473a65f5e 
  src/tests/authorization_tests.cpp 54bfb46a807677f4a4a2bb88dcb78a358cf5121a 



Tested on a range of Linux configurations on internal CI.


Benjamin Bannier

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message