-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get_attribute with a requirement as parameter #56
Comments
The example is invalid TOSCA in my opinion since it assigns values to properties (the "name' property of the 'host' capabilty) and input parameters('property_host_name' and 'attribute_host_name') that have not been previously defined. Ubicity generates the following error output:
|
According to Section 5.5.3 of TOSCA 1.3, |
There are many examples where operation input parameters are assigned without defined previously. |
My apologies, you are correct about |
In my opinion, it is OK for a node type definition to add input parameters to an interface definition that have not been previously defined in the corresponding interface type, but I believe it should be an error for a node template to add interface inputs that have not been previously defined in the corresponding interface definition. Could you point me to one of the examples in the spec so we can discuss this in the TOSCA Language Ad-Hoc? |
Have a look to examples in Sections 11.1.15.3, 11.1.16.3, 11.1.17.3.1, and 11.1.18.3.1 of TOSCA 1.3. |
Parsing the following service template
produces an error
As
get_property: [ SELF, host, name ]
is considered as a correct expression, thenget_attribute: [ SELF, host, name ]
shall be considered as a correct expression.The text was updated successfully, but these errors were encountered: