[OASIS Issue Tracker] (CAMP-203) User Mutability & POST to Operations

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

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

Anish Karmarkar commented on CAMP-203:
--------------------------------------

Depends on issue CAMP-201

> User Mutability & POST to Operations
> ------------------------------------
>
>                 Key: CAMP-203
>                 URL: https://issues.oasis-open.org/browse/CAMP-203
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>            Reporter: Michael Norman
>            Assignee: Anish Karmarkar
>
> Operations allow POST (the semantics of which is "perform the operation with these parameters").  This is different from PUT which would, for example, be used to change the tags or description of the Operation.  In most cases POST would be be allowed, but PUT not allowed.  
> However, it is conceivable that an assembly could have operations which, for a given instance/user were not allowed.  We need to clarify how this is handled through the API.  Would we mandate that the server only return Operations that the user could actually perform? or would the server be allowed to return Operations which the user wasn't allowed to perform with an indication that would allow the to be greyed-out in the user interface? If so we can't directly use the user mutability mechanisms, so we need to define how this works.
>   



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