description no The optional description string for the associated named operation. implementation no The optional implementation artifact name (e.g., a script file name within a TOSCA CSAR file). inputs no list of The optional list of input properties definitions (i.e., parameter definitions) for operation definitions that are within TOSCA Node or Relationship Type definitions. This includes when operation definitions are included as part of a Requirement definition in a Node Type. no list of The optional list of input property assignments (i.e., parameters assignments) for operation definitions that are within TOSCA Node or Relationship Template definitions. This includes when operation definitions are included as part of a Requirement assignment in a Node Template. The following is the list of recognized keynames to be used with the implementation keyname within a TOSCA operation definition: Keyname Type Description primary no The optional implementation artifact name (i.e., the primary script file name within a TOSCA CSAR file). dependencies no list of The optional ordered list of one or more dependent or secondary implementation artifact name which are referenced by the primary implementation artifact (e.g., a library the script installs or a secondary script). Grammar Operation definitions have the following grammars: Short notation The following single-line grammar may be used when only an operation’s implementation artifact is needed: <>: <> Extended notation for use in Type definitions The following grammar may be used in Node or Relationship Type definitions when additional information about the operation is needed: <>: description: <> implementation: <> inputs: <>
description no The optional description string for the associated named operation. implementation no The optional implementation artifact name (e.g., a script file name within a TOSCA CSAR file). inputs no list of The optional list of input properties definitions (i.e., parameter definitions) for operation definitions that are within TOSCA Node or Relationship Type definitions. This includes when operation definitions are included as part of a Requirement definition in a Node Type. no list of The optional list of input property assignments (i.e., parameters assignments) for operation definitions that are within TOSCA Node or Relationship Template definitions. This includes when operation definitions are included as part of a Requirement assignment in a Node Template. The following is the list of recognized keynames to be used with the implementation keyname within a TOSCA operation definition: Keyname Type Description primary no The optional implementation artifact name (i.e., the primary script file name within a TOSCA CSAR file). dependencies no list of The optional ordered list of one or more dependent or secondary implementation artifact name which are referenced by the primary implementation artifact (e.g., a library the script installs or a secondary script). Grammar Operation definitions have the following grammars: Short notation The following single-line grammar may be used when only an operation’s implementation artifact is needed: <>: <> Extended notation for use in Type definitions The following grammar may be used in Node or Relationship Type definitions when additional information about the operation is needed: <>: description: <> implementation: <> inputs: <>
TOSCA-Simple-Profile-YAML-v1.1-csprd01.docx