[ https://issues.oasis-open.org/browse/CAMP-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59260#comment-59260 ]
Gilbert Pilz commented on CAMP-178:
-----------------------------------
I agree in general but I have two comments.
1.) It makes sense to POST to "assemblies" and "plans" but not "services" (those are provisioned by the provider) nor any of the metadata collections ("formats", "type_definitions", "extensions", etc.).
2.) I'm uncomfortable with returning a 403 in cases where there no user, regardless of their privileges, would ever be able to invoke that HTTP method on that resource.
> 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)
