Mailing-List: contact issues-help@ariatosca.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ariatosca.incubator.apache.org
Date: Mon, 10 Jul 2017 22:11:00 +0000 (UTC)
From: "Avia Efrat (JIRA)" <jira@apache.org>
To: issues@ariatosca.apache.org
Message-ID: <JIRA.13086093.1499724435000.212242.1499724660174@Atlassian.JIRA>
In-Reply-To: <JIRA.13086093.1499724435000@Atlassian.JIRA>
References: <JIRA.13086093.1499724435000@Atlassian.JIRA> <JIRA.13086093.1499724435297@jira-lw-us.apache.org>
Subject: [jira] [Updated] (ARIA-313) unrequired operation inputs treated as
 required when starting an execution
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 10 Jul 2017 22:29:35 -0000


     [ https://issues.apache.org/jira/browse/ARIA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Avia Efrat updated ARIA-313:
----------------------------
    Description: 
Currently, not supplying a value to a node template operation input that is defined with `required: false` in its type passes the service creation stage, but when trying to execute a workflow on the service, the execution refuses to start, claiming that this input is missing.

Example:
{code}
# (assuming a 'create.sh' script is present)

tosca_definitions_version: tosca_simple_yaml_1_0

node_types:
  nodes.Container.Application.Kubernetes:
    derived_from: tosca.nodes.Root
    interfaces:
      Standard:
        create:
          inputs:
            labels:
              type: string
              required: false
          implementation: create.sh

topology_template:
  node_templates:
    web_app:
      type: nodes.Container.Application.Kubernetes
{code}
Running the install execution will alert that we didn't give a value to the `labels` input.

  was:
Currently, not supplying a value to a node template operation input that is defined with `required: false` in its type passes the service creation stage, but when trying to execute a workflow on the service, the execution refuses to start, claiming that this input is missing.

Example:
```
# (assuming a 'create.sh' script is present)

tosca_definitions_version: tosca_simple_yaml_1_0

node_types:
  nodes.Container.Application.Kubernetes:
    derived_from: tosca.nodes.Root
    interfaces:
      Standard:
        create:
          inputs:
            labels:
              type: string
              required: false
          implementation: create.sh

topology_template:
  node_templates:
    web_app:
      type: nodes.Container.Application.Kubernetes
```
Running the install execution will alert that we didn't give a value to the `labels` input.


> unrequired operation inputs treated as required when starting an execution
> --------------------------------------------------------------------------
>
>                 Key: ARIA-313
>                 URL: https://issues.apache.org/jira/browse/ARIA-313
>             Project: AriaTosca
>          Issue Type: Bug
>    Affects Versions: 0.1.0, 0.1.1, 0.2.0
>            Reporter: Avia Efrat
>
> Currently, not supplying a value to a node template operation input that is defined with `required: false` in its type passes the service creation stage, but when trying to execute a workflow on the service, the execution refuses to start, claiming that this input is missing.
> Example:
> {code}
> # (assuming a 'create.sh' script is present)
> tosca_definitions_version: tosca_simple_yaml_1_0
> node_types:
>   nodes.Container.Application.Kubernetes:
>     derived_from: tosca.nodes.Root
>     interfaces:
>       Standard:
>         create:
>           inputs:
>             labels:
>               type: string
>               required: false
>           implementation: create.sh
> topology_template:
>   node_templates:
>     web_app:
>       type: nodes.Container.Application.Kubernetes
> {code}
> Running the install execution will alert that we didn't give a value to the `labels` input.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)