[
https://issues.apache.org/jira/browse/MESOS-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257143#comment-15257143
]
Vinod Kone commented on MESOS-3914:
-----------------------------------
Moved some of the tickets from this epic to the Operator API v1 epic. MESOS-4791
> Make request format consistent across endpoints
> -----------------------------------------------
>
> Key: MESOS-3914
> URL: https://issues.apache.org/jira/browse/MESOS-3914
> Project: Mesos
> Issue Type: Epic
> Components: master
> Reporter: Alexander Rukletsov
> Labels: http, mesosphere, tech-debt
>
> We are inconsistent with the format of requests we expect for operator
> endpoints. For example, dynamic reservations take a string
> "slaveId={{<slaveID>}}&resources={{<JSON-for-resources>}}", while maintenance
> expects a {{JSON}} object representing {{maintenance::Schedule}} protobuf
> directly.
> We agreed to accept single {{JSON}} objects and provide a corresponding
> {{*Request}} protobuf to document the schema, leverage HTTP verbs where
> appropriate. Next steps are:
> * document how Mesos HTTP operator endpoints should be implemented;
> * convert all nonconformant endpoints via a deprecation cycle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
