ARIA exposes all defined attributes, even if they have no default value (in which case they will be null).
Note that three attributes (tosca_id, tosca_name, state) are automatically filled by ARIA, if they are available. Any node type inheriting from tosca.nodes.Root will have them. I'm not sure what you mean by "optional" or "mandatory": there is no way to define attributes that way. See section 3.5.10.2 in the spec. On Tue, Nov 14, 2017 at 4:05 PM, Steve Baillargeon < steve.baillarg...@ericsson.com> wrote: > Hi > The YAML spec is confusing about when the service or node instance > actually exposes the value of an attribute. > Does ARIA always implement and expose the values of all attribute > definitions (optional and mandatory) defined in normative types? > > Related observation: it is very strange that the YAML spec does not > support a REQUIRED keyname for the attribute definition. Then how do we go > about declaring an optional vs mandatory attribute definition in custom > type definitions? For now, I am almost ready to conclude that all > attributes SHOULD be exposed by the TOSCA orchestrator regardless if it is > required or not. > > -Steve >
