You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Thomas Bouron (JIRA)" <ji...@apache.org> on 2015/06/26 16:44:04 UTC
[jira] [Created] (BROOKLYN-153) RESP API Inconsistencies
Thomas Bouron created BROOKLYN-153:
--------------------------------------
Summary: RESP 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)