[
https://issues.apache.org/jira/browse/MESOS-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008803#comment-15008803
]
Lukas Loesche commented on MESOS-3914:
--------------------------------------
To me what would make the most sense is if the Content-Type of the POST/PUT
request is set to application/json and the body is a single JSON object. The
URI might container additional parameters that determine how the operation is
performed. E.g. "?force=true" to force the operation. But all data regarding
the operation itself should be contained in that single JSON object.
> Make request format consistent across endpoints
> -----------------------------------------------
>
> Key: MESOS-3914
> URL: https://issues.apache.org/jira/browse/MESOS-3914
> Project: Mesos
> Issue Type: Improvement
> Components: master
> Reporter: Alexander Rukletsov
> Labels: 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 should agree on the input: either we expect a string with key-value pairs,
> where values can be {{JSON}} objects, or we request {{JSON}} directly.
> Once we agree on the approach, we should document the outcome and convert all
> nonconformant endpoints via a deprecation cycle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
