[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-30) Parameter Scheme
[ http://tools.oasis-open.org/issues/browse/CAMP-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32936#action_32936 ]
Alex Heneveld commented on CAMP-30:
-----------------------------------
We are very close. The stumbling block appears to be whether we want to make it formally and testably discoverable whether a parameter becomes an attribute. This affects 6.6.1 which currently does this in a half-baked way.
If the answer is no (this is not so important that we have big scaffolding) then I suggest the following text:
*Parameters allow customizing Resources upon creation. Parameters MAY have the same name as an Attribute on the Resource. In such cases the implementation SHOULD set the Attribute to take the value of the Parameter OR clearly document the behaviour.*
If the answer is yes (personally I think that's the wrong answer now but...) then I believe we should address this properly with a new attribute on ParameterDefinition, e.g. "autowired" or "passthrough" or "mutableConfiguration" or something.
> Parameter Scheme
> ----------------
>
> Key: CAMP-30
> URL: http://tools.oasis-open.org/issues/browse/CAMP-30
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Improvement
> Components: Spec
> Reporter: Adrian Otto
> Assignee: Adrian Otto
> Priority: Critical
>
> Create a well defined template parameter scheme that can be used to express special labels in template resource attributes that are used for supplying values upon instantiating entities using the template. In addition to a template parameter label, we also need a standard mechanism to specify values for the labels when using the API.
> This feature can be used for supplying a unique name to an Application Assembly at the time it is created and started. This would allow multiple Application Assemblies to be created from the same template to run concurrently, and offer a way to easily tell them apart from each other. The scheme should be flexible such that it works for Component Templates as well, so that it can be used for passing in configuration parameters that are employed by a downstream configuration management system.
--
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]