[OASIS Issue Tracker] Commented: (CAMP-74) Plans resource does not have Parameters

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

    [ http://tools.oasis-open.org/issues/browse/CAMP-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35840#action_35840 ] 

Gilbert Pilz commented on CAMP-74:
----------------------------------

This issue is tricky because the Plan resource is unique among CAMP resources. It's schema is actually defined in terms of YAML, and only includes the nodes/attributes that are valid in a camp.yaml file. If we say that the Plan resource *also* includes a 'parameterDefinitionsUri' attribute, then doing a GET on a Plan resource will yield a representation that is not a valid camp.yaml file. If we don't use ParameterDefinitions to define the parameters that can be applied on a POST request to a Plan resource, we will have to define a unique way of advertising this information.

> Plans resource does not have Parameters
> ---------------------------------------
>
>                 Key: CAMP-74
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-74
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>         Environment: WD18
>            Reporter: Gilbert Pilz
>
> We allow Parameters for PlatformComponentTemplate resources, but not the ApplicationComponentTemplate resources. This seems inconsistent and wrong. There are many use cases for parameterizing ApplicationComponentTemplates. For example, an Application Admin may want to deploy a WAR file using a context name other than the default.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira