[jira] [Commented] (BROOKLYN-153) REST API Inconsistencies

["Thomas Bouron (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BROOKLYN-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602998#comment-14602998 ] 

Thomas Bouron commented on BROOKLYN-153:
----------------------------------------

Actually, the last 3 requires the {{type}}, not the {{id}}. The documentation is clearly misleading

> REST API Inconsistencies
> ------------------------
>
>                 Key: BROOKLYN-153
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-153
>             Project: Brooklyn
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Thomas Bouron
>
> There are inconsistencies with the REST API for the {{/catalog/*}} endpoints. For example, If I want to get an application with the a specific {{type}} or {{id}}, I can use either:
> {code}
> GET /v1/catalog/entities/{type} (returns the latest version)
> GET /v1/catalog/entities/{id} (returns the specific version as id = {type}:{version})
> GET /v1/catalog/application/{id}/{version}
> GET /v1/catalog/entities/{id}:{version}
> GET /v1/catalog/entities/{id}/{version}
> {code}
> This is really confusing, especially the last 3 as the {{id}} already contains the {{version}}. These endpoints should rather take the {{type}} instead of {{id}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)