[
https://issues.apache.org/jira/browse/MESOS-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt DeBoer updated MESOS-6099:
-------------------------------
Description:
For the mesos HTTP api documented here:
http://mesos.apache.org/documentation/latest/endpoints/, most of the individual
paths are lacking info about which HTTP verbs are accepted, and what affect
they have.
In order to determine the accepted verbs and their behavior, one must try them
and see what happens.
was:
For the mesos HTTP api documented here:
http://mesos.apache.org/documentation/latest/endpoints/, most of the individual
paths are lacking info about which HTTP verbs are accepted, and what affect
they have.
In order to determine the accepted verbs and their behavior, one must try them
and see what happens.
Some (like /maintenance/schedule for example) have different method information
embedded in the descriptions, but most API documentation IHMO typically treats
each (verb + path) as a unique endpoint.
> Mesos endpoints documentation is missing HTTP verbs
> ---------------------------------------------------
>
> Key: MESOS-6099
> URL: https://issues.apache.org/jira/browse/MESOS-6099
> Project: Mesos
> Issue Type: Documentation
> Components: documentation, HTTP API
> Affects Versions: 1.0.1
> Reporter: Matt DeBoer
> Priority: Minor
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> For the mesos HTTP api documented here:
> http://mesos.apache.org/documentation/latest/endpoints/, most of the
> individual paths are lacking info about which HTTP verbs are accepted, and
> what affect they have.
> In order to determine the accepted verbs and their behavior, one must try
> them and see what happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
