[OASIS Issue Tracker] (CAMP-181) is it an error to even select a non-consumer mutable attribute with PUT and select_attr

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

Gilbert Pilz created CAMP-181:
---------------------------------

             Summary: is it an error to even select a non-consumer mutable attribute with PUT and select_attr
                 Key: CAMP-181
                 URL: https://issues.oasis-open.org/browse/CAMP-181
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: Bug
          Components: Spec
            Reporter: Gilbert Pilz
            Assignee: Gilbert Pilz
            Priority: Minor


The order of error checking in simple PUT requests and PUT requests using select_attr can create inconsistent behaviors. We have agreed that a PUT request should be processed as a request to completely replace a resource. Immutable and non-consumer mutable attributes must be included in the body of such requests (to do otherwise would indicate a desire to delete them), but must match the values of the existing resource.

This begs the question of how to process the inclusion of immutable and non-consumer mutable attributes in the value of the 'select_attr' attribute. Naively one could treat the inclusion of such attributes as an error without regards to the value of those attributes in the request body. Doing this, however, runs counter to our notion of treating select_attr as a mask. Regardless of whether select_attr is used or not, the treatment of immutable and non-consumer mutable attributes should be consist across all HTTP methods, including PUT.



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