[OASIS Issue Tracker] (CAMP-199) type_definition resource should indicate consumer mutability

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/CAMP-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61448#comment-61448 ] 

Gilbert Pilz commented on CAMP-199:
-----------------------------------

I had an AI to investigate how we structured type_definitions and attribute_definitions. type_definitions contain a reference to a collection of attribute_definitions. To determine whether or not a resource is modifiable by a user a Consumer would have to do the following:

1.) GET the resource (doesn't really count - you always have to do this).
2.) GET the type_definition *instance* (see 201) for that resource
3.) GET the attribute_definition collection from that type_definition
4.) iterate through 'items' array looking for an attribute_definition with "consumer_mutable": true

This proposal basically requires the Provider to continuously pre-calculate steps 3 & 4 to save the Consumer the extra trip of step 3.

> type_definition resource should indicate consumer mutability
> ------------------------------------------------------------
>
>                 Key: CAMP-199
>                 URL: https://issues.oasis-open.org/browse/CAMP-199
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>    Affects Versions: 1.2
>            Reporter: Gilbert Pilz
>            Assignee: Anish Karmarkar
>            Priority: Minor
>             Fix For: 1.2
>
>
> Right now the only way a Consumer of the API can determine if a resource can be changed is to enumerate all of the attribute definitions and see if any of those are consumer mutable. For convenience this information should be rolled up into an attribute of the type_definition.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)