[
https://issues.apache.org/jira/browse/DTACLOUD-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547365#comment-13547365
]
Ronelle Landy commented on DTACLOUD-339:
----------------------------------------
Question: Looking at the mock provider:
<link href='http://localhost:3001/api/instances' rel='instances'>
<feature name='metrics' rel='create'>
<param name='metrics' />
</feature>
<feature name='realm_filter' rel='index'>
<param name='realm_id' />
</feature>
<feature name='user_name' rel='create'>
<param name='name' />
</feature>
<feature name='user_data' rel='create'>
<param name='user_data' />
</feature>
<feature name='authentication_key' rel='create'>
<param name='keyname' />
</feature>
<feature name='authentication_key' rel='show'>
</feature>
authentication_key is listed twice. Is that correct? Is it a result of needing
two different 'rel' values?
> 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
