[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (CAMP-179) POST parameters are contradictory and/or confusing
[ https://issues.oasis-open.org/browse/CAMP-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Pilz updated CAMP-179: ------------------------------ Proposal: Add 'name', 'description', and 'tags' to the list in Section 5.9.2. Also add them to the list of parameters accepted by the "plans resource" in 5.14.2. Detailed proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/55505/camp-spec-v1.2-wd01-issue-179-v1.doc was:Add 'name', 'description', and 'tags' to the list in Section 5.9.2. Also add them to the list of parameters accepted by the "plans resource" in 5.14.2. > POST parameters are contradictory and/or confusing > -------------------------------------------------- > > Key: CAMP-179 > URL: https://issues.oasis-open.org/browse/CAMP-179 > 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.9.2 of CAMP 1.1, it states that: > "The assemblies resource accepts the pdp_uri, plan_uri, pdp_file, or plan_file parameters to create a new assembly resource upon a POST. The assemblies resource SHALL indirectly reference parameter_definition resources that describes the pdp_uri, plan_uri, pdp_file, and plan_file parameters. [RMR-03]" > However, one of the use cases we wanted to cover with respect to creating a new application was the case in which the client provided the 'name' and/or 'description' and/or 'tags' of the new application in parameter(s) to the POST method. A vestige of this notion still lingers on in the examples in Sections 6.11.1, 6.11.2.1, 6.12.1, etc. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]