[
https://issues.apache.org/jira/browse/MESOS-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110273#comment-15110273
]
Guangya Liu commented on MESOS-3838:
------------------------------------
Thanks [~adam-mesos], yes, here what I want to do is a code clean up and want
to make the {{teardown}} logic same as other opearations such as
{{authorizeDestroyVolume}}, {{authorizeCreateVolume}} , it may not visible to
end user, but it can definitely help developers under code logic easily if all
operations has similiar logic/code patch for authorize.
This is not a blocker for MESOS-4154, we can treat them separately but both of
those two JIRA related to {{teardown}}.
> Put authorize logic for teardown into a common function
> -------------------------------------------------------
>
> Key: MESOS-3838
> URL: https://issues.apache.org/jira/browse/MESOS-3838
> Project: Mesos
> Issue Type: Bug
> Reporter: Guangya Liu
> Assignee: Guangya Liu
>
> The mesos now have {{authorizeTask}}, {{authorizeFramework}} and may have
> {{authorizeReserveResource}} and {{authorizeUnReserveResource}} later.
> But now the {{Master::Http::teardown()}} is putting the authorize logic in
> the {{Master::Http::teardown()}} itself, it is better to put authorize logic
> for teardown into a common function {{authorizeTeardown()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
