[OASIS Issue Tracker] (CAMP-201) Consumer mutability of attributes and attribute types

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

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

Anish Karmarkar commented on CAMP-201:
--------------------------------------

Two comments on the proposal at  https://www.oasis-open.org/apps/org/workgroup/camp/download.php/57401/mutability_outline.txt
(1) With our decision not to abuse the type system to provide instance-specific metadata, I image that we'll get the type_definition pointer out of the instance. The only reason we included the type_definition pointer was to allow us to point to instance-specific type.
(2) We should think about separating the metadata from the instance data. When I do a GET on a Plan I want to see what the plan enables not necessarily what I can update. I.e., I want to know what is in the Plan and mutability is not part of it. Moreover, consumer mutability is probably the first of the many kind of instance-specific metadata we (or extension creators) might want to add. We should think about whether this needs to be in a separate resource or included in headers.

> Consumer mutability of attributes and attribute types
> -----------------------------------------------------
>
>                 Key: CAMP-201
>                 URL: https://issues.oasis-open.org/browse/CAMP-201
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>    Affects Versions: 1.2
>            Reporter: Anish Karmarkar
>            Assignee: Anish Karmarkar
>            Priority: Critical
>
> The spec currently defines consumer mutability of an attribute in the attribute type definition. Questions have been raised about whether that is appropriate. Few scenarios that complicate this:
> 1) Collection type 'items' attribute may be mutable or not depending on the kind of collection.
> 2) the consumer mutability of an attribute may depend on an instance not the type. Moving this to the type necessitates unnecessary invention of additional types
> 3) the mutability of an attribute may depend on other factors such as authorization/credentials of the consumer or it may change with time (because changing the attribute value may make something else inconsistent).
> Issues 180, 196, and 199 depend on resolution of this issue.



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