[
https://issues.apache.org/jira/browse/ARIA-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ran Ziv updated ARIA-172:
-------------------------
Description:
Add support for custom data types (complex types defined in the
service-template) in inputs validation (service inputs, execution inputs, task
inputs).
Note that data-types are not currently stored as part of the service-template
or service models, and are currently only used during parsing phase.
Note: This issue should also take care of the consolidation of the constraints
mechanism over at
{{extensions/aria_extension_tosca/simple_v1_0/modeling/data_type.py}} along
with the new constraints mechanism at
{{extensions/aria_extension_tosca/simple_v1_0/modeling/constraints.py}}.
was:
Add support for custom data types (complex types defined in the
service-template) in inputs validation (service inputs, execution inputs, task
inputs).
Note that data-types are not currently stored as part of the service-template
or service models, and are currently only used during parsing phase.
> Support for custom data-types in inputs validation
> --------------------------------------------------
>
> Key: ARIA-172
> URL: https://issues.apache.org/jira/browse/ARIA-172
> Project: AriaTosca
> Issue Type: Story
> Reporter: Ran Ziv
> Priority: Minor
>
> Add support for custom data types (complex types defined in the
> service-template) in inputs validation (service inputs, execution inputs,
> task inputs).
> Note that data-types are not currently stored as part of the service-template
> or service models, and are currently only used during parsing phase.
> Note: This issue should also take care of the consolidation of the
> constraints mechanism over at
> {{extensions/aria_extension_tosca/simple_v1_0/modeling/data_type.py}} along
> with the new constraints mechanism at
> {{extensions/aria_extension_tosca/simple_v1_0/modeling/constraints.py}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
