Here, I have used the get_attribute in the input defined in the second
level, for which it returns me the dictionary object.
inputs:
payload: {
"config": {get_attribute: [ SELF, vmme_configuration ]}}
When I use the get_attribute in inputs defined in the first level it returns
me none.
inputs:
config: {get_attribute: [ SELF, vmme_configuration ]}
Please find the service template below.
node_types:
my_Node_Server:
derived_from: tosca.nodes.Root
attributes:
vmme_configuration:
type: string
interfaces:
Standard:
create:
implementation: sample > sample.sample_test.call_test
inputs: {}
configure:
implementation: sample > sample.sample_test.call_name
inputs: {}
topology_template:
node_templates:
v_mme:
type: my_Node_Server
interfaces:
Standard:
configure:
inputs:
payload: {
"config": {get_attribute: [ SELF, vmme_configuration ]}}
config: {get_attribute: [ SELF, vmme_configuration ]}
Regards,
Vaishali.
-----Original Message-----
From: Tal Liron [mailto:[email protected]]
Sent: Tuesday, December 05, 2017 2:06 PM
To: [email protected]
Subject: Re: get_attribute function not supporting SELF as
<modelable_entity_name>
Thanks for the report. Do you possibly have a minimal TOSCA template we can
use to reproduce the error?
On Tue, Dec 5, 2017 at 8:29 AM, Vaishali Krishnamurthy <
[email protected]> wrote:
> Hi,
>
> We have observed the attribute resolution is not proper when we use
> SELF as <modelable_entity_name> in get_attribute function and it
> works fine when we use the node name as <modelable_entity_name> .
> With SELF it takes the default value. Could you confirm if there is any
> fix for this issue ?
>
>
> Regards,
>
> Vaishali
>
