Repository: mesos Updated Branches: refs/heads/master aa39faa6d -> 90f3fec71
Updated Authorization documentation to use /teardown endpoint. With Mesos 0.23 the /shutdown endpoint has been deprecated in favor of the /teardown endpoint. See MESOS-2697 for details. Review: https://reviews.apache.org/r/36774 Project: http://git-wip-us.apache.org/repos/asf/mesos/repo Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/90f3fec7 Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/90f3fec7 Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/90f3fec7 Branch: refs/heads/master Commit: 90f3fec71535bdf9c0cd5fc90c62e19a86b92470 Parents: aa39faa Author: Joerg Schad <[email protected]> Authored: Mon Jul 27 14:17:12 2015 +0200 Committer: Till Toenshoff <[email protected]> Committed: Mon Jul 27 14:17:12 2015 +0200 ---------------------------------------------------------------------- docs/authorization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mesos/blob/90f3fec7/docs/authorization.md ---------------------------------------------------------------------- diff --git a/docs/authorization.md b/docs/authorization.md index 2634fbf..2a5e747 100644 --- a/docs/authorization.md +++ b/docs/authorization.md @@ -46,7 +46,7 @@ For example, when a framework (re-)registers with the master, the "register_fram Similarly, when a framework launches a task(s), "run_tasks" ACLs are checked to see if the framework (`FrameworkInfo.principal`) is authorized to run the task/executor as the given `user`. If not authorized, the launch is rejected and the framework gets a TASK_LOST. -In the same vein, when a user/principal attempts to shutdown a framework through the "/shutdown" HTTP endpoint on the master, "shutdown_frameworks" ACLs are checked to see if the `principal` is authorized to shutdown the given framework. If not authorized, the shutdown is rejected and the user receives an `Unauthorized` HTTP response. +In the same vein, when a user/principal attempts to shutdown a framework through the "/teardown" HTTP endpoint on the master, "shutdown_frameworks" ACLs are checked to see if the `principal` is authorized to shutdown the given framework. If not authorized, the shutdown is rejected and the user receives an `Unauthorized` HTTP response. There are couple of important things to note: @@ -151,7 +151,7 @@ There are couple of important things to note: } -8. Only `ops` principal can shutdown any frameworks through "/shutdown" HTTP endpoint. +8. Only `ops` principal can shutdown any frameworks through "/teardown" HTTP endpoint. { "permissive" : false,
