[
https://issues.apache.org/jira/browse/BROOKLYN-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608420#comment-14608420
]
ASF GitHub Bot commented on BROOKLYN-153:
-----------------------------------------
GitHub user tbouron opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/729
[BROOKLYN-153] Update the REST API documentation for the catalog endpoints
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tbouron/incubator-brooklyn rest-api-docs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/729.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #729
----
commit 08790a76b28f7e2d560c873118af0379ecb60895
Author: Thomas Bouron <[email protected]>
Date: 2015-06-30T14:55:53Z
[BROOKLYN-153] Update the REST API documentation for the catalog endpoints
----
> 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)
