[OASIS Issue Tracker] (CAMP-178) description of "plan resource" does not say you can use HTTP DELETE to delete a plan resource

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

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

Mike Norman commented on CAMP-178:
----------------------------------

I think it would be more straightforward to define a default set of verbs:  GET and POST for the list "resources" and  PUT, PATCH, GET and DELETE for the single resources.  Anything outside of this set of verbs you get 405s.

Then a specific implementation may issue 403s for things it chooses not to allow from this set, either based on implementation constraints or on ACL (which would be provided by an extension). 


> description of "plan resource" does not say you can use HTTP DELETE to delete a plan resource
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMP-178
>                 URL: https://issues.oasis-open.org/browse/CAMP-178
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>            Reporter: Gilbert Pilz
>            Assignee: Gilbert Pilz
>            Priority: Minor
>
> In Section 5.5 of CAMP 1.1 we state that:
> "Providers SHALL support the HTTP GET, PUT, and PATCH methods on all of the resources defined in this section. [RE-53] Requirements for the support of additional HTTP methods are outlined in the descriptions of each resource below."
> For the "assembly" and "component" resources we require that providers support the DELETE method to remove the resource (requirements RE-61 and RE-62 respectively), but nowhere do we state that providers must support the DELETE method on "plan" resources.



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