[
https://issues.apache.org/jira/browse/DTACLOUD-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547388#comment-13547388
]
David Lutterkort commented on DTACLOUD-339:
-------------------------------------------
The second one isn't necessary and should be omitted, as clients can tell from
the response they get whether the authentication_key is included in the
instance details or not.
We really only need a feature for things that change what parameters a user can
include with their requests.
> RFE: Indicate the operation for certain feature in /api
> -------------------------------------------------------
>
> Key: DTACLOUD-339
> URL: https://issues.apache.org/jira/browse/DTACLOUD-339
> Project: DeltaCloud
> Issue Type: New Feature
> Reporter: Michal Fojtik
> Assignee: Michal Fojtik
>
> Currently, when client get list of feature in /api he got something like:
> <link href="http://localhost:3001/api/instances"; rel="instances">
> <feature name="metrics"></feature>
> <feature name="realm_filter"></feature>
> <feature name="user_name"></feature>
> <feature name="user_data"></feature>
> <feature name="authentication_key"></feature>
> </link>
> Unfortunately this does not tell client for what operations does this feature
> apply. Like the 'realm_filter' apply for the :index operation but the
> ':user_data' is valid for the create operation.
> I suggest to add something like:
> <link href="http://localhost:3001/api/instances"; rel="instances">
> <feature name="metrics" rel="create"></feature>
> <feature name="realm_filter" rel="index"></feature>
> ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
